How do I install the Using Aegis skill?

Run npx skillmds add thedixitjain/using-aegis in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Using Aegis skill do?

Use when starting a turn or checking Aegis skill routing. It is listed under Coding & Dev Tools on SkillMD.

Is Using Aegis safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Using Aegis?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Using Aegis free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Using Aegis?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Using Aegis by thedixitjain — Agent Skill

Name: Using Aegis
Rating: 4.2 (5 reviews)
Author: thedixitjain

File contents

Skip for subagents.

Hot Path

User/project instructions outrank Aegis.
Active codebase question/"what next": check README/ADR/rules/baseline, else bounded index-first scan. Non-trivial owners passively use relevant CONTEXT-MAP.md/CONTEXT.md; compose establishing-project-context only on semantic delta/conflict. Create baselines only with evidence.
Direct grilling or plan/design pressure-tests (grill me, grill this plan, 审问我, 盘问我, 拷问我) route to brainstorming; literal/explanatory uses do not.
/aegis-goal or Aegis goal: loads goal-framing before routing.
Bug, failure, regression, or unexpected behavior routes to systematic-debugging; quick bug lane owns Change Necessity before source edits.
Classify before implementation/start/resume/compaction. Low: intent, baseline, verification. Medium/high: baseline read-set + plan. TDD: off=no auto route/load; auto=strict/light/skipped; explicit request applies. Spec Brief or Design Spec only for complex, ambiguous, contract, cross-module work; shared/core/contract/cross-module never low without evidence. Source edits/new paths: owner workflow surfaces Change Necessity.
Non-tiny loaded skill: at the first substantive user-visible stage say why Aegis is shaping work/risk; do not wait for the user to ask. structured trace only for audit/debug/release/long-task review/asked; Trace Digest does not route. Tiny stays implicit.
ArchitectureReviewRequired: yes for medium/high architecture/contract/ cross-module/owner/source-of-truth/fallback/adapter/baseline; carry to verification.
Workspace support is lazy; use configured Aegis workspace support only when records needed. Fast Q&A/status/tiny edits write no files.
Load smallest needed skill/reference.
Tool/log/memory/search outputs are evidence candidates, not prompt payloads; summary first, large input index->window->excerpt.
No history/sessions/transcripts/large logs by default; bound requested evidence by scope/time/lines.
Unclear host tool-name mapping: read smallest relevant reference.

Contract: Route: fast-path; Aegis Reason Note.

Source: hashgraph-online/awesome-codex-plugins → plugins/GanyuanRan/Aegis/skills/using-aegis/SKILL.md

---name: using-aegisdescription: Use when starting a turn or checking Aegis skill routing.--- <SUBAGENT-STOP>Skip for subagents.</SUBAGENT-STOP> <EXTREMELY-IMPORTANT> You have Aegis. Load explicit/relevant Aegis skill before response/action; otherwise proceed normally. </EXTREMELY-IMPORTANT> ## Hot Path 1. User/project instructions outrank Aegis. 2. Active codebase question/"what next": check README/ADR/rules/baseline, else bounded index-first scan. Non-trivial owners passively use relevant `CONTEXT-MAP.md`/`CONTEXT.md`; compose `establishing-project-context` only on semantic delta/conflict. Create baselines only with evidence. 3. Direct grilling or plan/design pressure-tests (`grill me`, `grill this plan`, `审问我`, `盘问我`, `拷问我`) route to `brainstorming`; literal/explanatory uses do not. 4. `/aegis-goal` or `Aegis goal:` loads `goal-framing` before routing. 5. Bug, failure, regression, or unexpected behavior routes to `systematic-debugging`; quick bug lane owns Change Necessity before source edits. 6. Classify before implementation/start/resume/compaction. Low: intent, baseline, verification. Medium/high: baseline read-set + plan. TDD: off=no auto route/load; auto=strict/light/skipped; explicit request applies. Spec Brief or Design Spec only for complex, ambiguous, contract, cross-module work; shared/core/contract/cross-module never low without evidence. Source edits/new paths: owner workflow surfaces Change Necessity. 7. Non-tiny loaded skill: at the first substantive user-visible stage say why Aegis is shaping work/risk; do not wait for the user to ask. structured trace only for audit/debug/release/long-task review/asked; `Trace Digest` does not route. Tiny stays implicit. 8. ArchitectureReviewRequired: yes for medium/high architecture/contract/ cross-module/owner/source-of-truth/fallback/adapter/baseline; carry to verification. 9. Workspace support is lazy; use configured Aegis workspace support only when records needed. Fast Q&A/status/tiny edits write no files. 10. Load smallest needed skill/reference. 11. Tool/log/memory/search outputs are evidence candidates, not prompt payloads; summary first, large input index->window->excerpt. 12. No history/sessions/transcripts/large logs by default; bound requested evidence by scope/time/lines. 13. Unclear host tool-name mapping: read smallest relevant reference. Contract: `Route: fast-path`; `Aegis Reason Note`. --- **Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/GanyuanRan/Aegis/skills/using-aegis/SKILL.md`

Frequently asked questions