Skip to content
Back to skills

Using Aegis

ASecurity

Use when starting a turn or checking Aegis skill routing.

  • 9 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 9, 2026
code-qualitygoapi

Works with

  • api

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned September 9, 2026

npx -y skills add Undermybelt/hermes-skills --skill using-aegis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Using Aegis?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Using Aegis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/undermybelt-using-aegis/badge)](https://www.skillsdirectory.com/skills/undermybelt-using-aegis)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: using-aegis
description: Use when starting a turn or checking Aegis skill routing.
---

<SUBAGENT-STOP>Subagents skip this skill.</SUBAGENT-STOP>

<EXTREMELY-IMPORTANT>
You have Aegis.

Before any response/action, check if an Aegis skill is explicit or clearly
relevant. Load only that skill; otherwise proceed normally.
</EXTREMELY-IMPORTANT>

## Hot Path Rules

1. User and project instructions outrank Aegis.
2. Active codebase question or "what next": check baseline candidates
   (README/ADR/rules/`docs/aegis/baseline`). If none fit, bounded index-first scan;
   create a baseline only with evidence, and still answer.
3. `/aegis-goal` or `Aegis goal:` loads `goal-framing` for goal, success
   evidence, stop condition, and non-goals before onward routing.
4. Classify before implementation/start/resume/compaction. Low: concise intent
   + baseline check + TDD Route + verification. Medium/high: baseline read-set + plan.
   TDD Route: auto=strict/light/skipped; off=no automatic TDD,
   verification stays. Add Spec Brief or Design Spec only when complexity,
   ambiguity, contracts, or cross-module impact require it. Contract/shared/core
   or cross-module changes are never low without evidence.
5. Aegis Reason Note: say why Aegis is shaping non-trivial skill/stage work; tiny fast-path may stay implicit; structured trace only for audit/debug/release/long-task review or asked.
6. Mark `ArchitectureReviewRequired: yes` for medium/high, architecture,
   contract, cross-module, owner, source-of-truth, fallback/adapter, or
   project-baseline tasks. Carry it to `verification-before-completion`.
7. Workspace support is lazy. Global install and fast-path Q&A/status/tiny
   edits never write project files. Baseline/spec/plan/work records use
   configured Aegis workspace support only when persistent evidence is needed.
8. Load the smallest needed skill/reference.
9. Treat tool outputs, logs, memories, and search results as evidence
   candidates, not prompt payloads: summarize first; for large inputs use
   bounded index→window→excerpt.
10. Do not read historical sessions, transcripts, `history.jsonl`,
   `.codex/sessions`, `~/.claude/projects`, or large logs by default. Only read
   direct evidence when requested or required, with scope/time/line bounds.
11. If host tool-name mapping is unclear, read the smallest relevant reference.

Contract when useful: `Route: fast-path`; `Aegis Reason Note`; `Why`; `Next`.

Files in this skill

  • SKILL.md2.4 KB
  • references/antigravity-tools.md3.2 KB
  • references/codex-tools.md4 KB
  • references/copilot-tools.md2.1 KB
  • references/gemini-tools.md1.5 KB
  • references/skill-discipline.md10 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…