Menu
Use when starting a turn or checking Aegis skill routing.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/hashgraph-online/awesome-codex-plugins --skill using-aegisThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | using-aegis |
| description | Use when starting a turn or checking Aegis skill routing. |
Skip for subagents.
You have Aegis. Load explicit/relevant Aegis skill before response/action; otherwise proceed normally.CONTEXT-MAP.md/CONTEXT.md; compose establishing-project-context only
for semantic delta/conflict. Create baselines only with evidence.grill me, grill this plan, 审问我, 盘问我, 拷问我) route to brainstorming; literal/explanatory uses do not./aegis-goal or Aegis goal: loads goal-framing before routing.systematic-debugging; quick bug lane owns Change Necessity before source edits.TaskStartSnapshot.
Complexity, TDD, planning, or subagents alone do not
justify branch/worktree creation.Trace Digest does not route. Tiny stays implicit.Contract: Route: fast-path; Aegis Reason Note.
Coordinate agents via the AMQ CLI for file-based inter-agent messaging. Use this skill whenever you need to send messages to another agent (codex, claude, or any named handle), check your inbox, drain queued messages, set up co-op mode between agents, join a swarm team, route messages across projects, or diagnose delivery issues. Also use it when you receive a message and need to know how to reply, inspect receipts, or handle priority. Covers any multi-agent coordination task where agents need to talk to each other — review requests, questions, status updates, decision threads, wake notifications, and orchestrator integration (Symphony, Kanban). For collaborative spec/design workflows specifically, prefer the /amq-spec skill which provides structured phase-by-phase guidance. Not intended for distributed systems design (RabbitMQ, Kafka), CI/CD pipelines, or single-agent tasks with no partner.
Parallel-research-then-converge design workflow between two agents. Use this skill when the user wants two agents to independently think through a design problem before aligning on a solution — "spec X with codex", "design X together", "both agents think through X", "brainstorm architecture together", "parallel research then joint proposal", "think through separately then align", "careful thought from both sides before coding", or any variation where the user wants collaborative design rather than just splitting implementation work. Also use this when you receive a message labeled workflow:spec and need to know the correct receiver-side protocol. Not for sending simple messages or reviews (use /amq-cli), implementing completed designs, or creating document templates.
Use when defining new features, product behavior, UI/component design, architecture choices, contract changes, or ambiguous medium/high-complexity work before implementation, or when the user asks to grill or pressure-test a plan or design.
