Borrowing it
Nothing to install: this file belongs to aidemd-mcp/server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aidemd-mcp/server/main/.claude/skills/aide/SKILL.mdgit clone --depth 1 https://github.com/aidemd-mcp/serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/aidemd-mcp/server/aide)<a href="https://agentmods.dev/skills/aidemd-mcp/server/aide"><img src="https://agentmods.dev/badge/skills/aidemd-mcp/server/aide/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aidemd-mcp/server/aide"><img src="https://agentmods.dev/badge/skills/aidemd-mcp/server/aide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00230 | $0.14296 |
| Opus 5.5 | $0.00092 | $0.05718 |
| Sonnet 5.5 | $0.00046 | $0.02859 |
| Haiku 4.5 | $0.00023 | $0.01430 |
Grade A, and why
aide scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 611 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aide — Orchestrator
Conversational entry point for the full AIDE pipeline. Gathers context from the user, then drives each phase by delegating to specialized agents — spinning up fresh context for every stage and handing off via files.
This skill is the source of truth for the orchestrator. The /aide slash command (in .claude/commands/aide.md) is a thin signpost that routes to this skill — the prose lives here so the methodology, boot sequence, and constraints surface together with the skill's frontmatter description in the available-skills listing.
MANDATORY BOOT SEQUENCE
STOP. Do not respond to the user's request yet. Do not analyze it. Do not classify it.
Boot fires on EVERY invocation of this skill — no exceptions. It is sequential, not parallel — brain status gates everything else. There is no point loading docs and the intent tree if the brain isn't wired.
Step 1 — Call aide_info
This is your only first call. No Read, no aide_discover, no other tool.
Step 2 — Brain status (hard gate)
The brain is the pipeline's durable memory. If it isn't wired, the pipeline can't run.
aide_info returns one of five brain.status values. Branch on them exactly:
-
ok— continue to Step 3. -
no-brain-aide— thebrain.aideconfig file is missing (.aide/config/brain.aidedoes not exist). STOP boot. Do NOT read docs. Do NOT callaide_discover. Tell the user in one line, conversational tone — e.g.:The brain config file (
brain.aide) is missing — let's set that up first.Then invoke the config flow:
Skill(skill="aide:brain", args="config")After the skill returns, halt — the skill itself scaffolds
brain.aide, handles the sync, and asks the user to restart. -
brain-aide-invalid— thebrain.aideconfig file is present but falls short of the required-section contract.brain.faultsays how. STOP boot. Do NOT read docs. Do NOT callaide_discover. Tell the user in one line what is wrong:fault.kind === "missing-sections"→ name the sections fromfault.sections, e.g.:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago Changed 7fc2acbabfa1
- 3d ago Changed · +13 lines 86fe8b9be070
- 4d ago Changed · +43 lines · +7 tokens per session 2ee9aa6e73d1
- 19d ago Changed · -4 lines 065debf03ea9
- 20d ago Changed · +58 lines · +15 tokens per session 1ac20d1e8840
- 2mo ago First seen · 501 lines · 208 tokens per session scan A 9fab6e7e3ad5
aide is a skill published in the GitHub repository aidemd-mcp/server (4 stars, last pushed 2d ago), licensed MIT. It adds 230 tokens to every session and 14,296 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.