Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/aidemd-mcp/server/aidenpx skills add aidemd-mcp/server --skill aidegit 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.svg" alt="Measured on agentmods" 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 | $0.00208 | $0.09715 |
| Opus 5 | $0.00104 | $0.04858 |
| Sonnet 5 | $0.00042 | $0.01943 |
| Haiku 4.5 | $0.00021 | $0.00971 |
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 3d 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 — 501 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 four brain.status values. Branch on them exactly:
-
ok— continue to Step 3. -
no-brain-aide— thebrain.aideconfig file is missing. 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")The config flow scaffolds
brain.aideand syncs it into.mcp.json. After it returns, halt — the user must runnpx @aidemd-mcp/server@latest syncand then re-run/aide. -
no-mcp-entry— the brain backend is not wired into.mcp.json. STOP boot. Do NOT read docs. Do NOT callaide_discover. Tell the user in one line — e.g.:The brain isn't wired up yet — let's fix that first.
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.
- 3d ago First seen · 501 lines · 208 tokens per session scan A 9fab6e7e3ad5
aide is a skill published in the GitHub repository aidemd-mcp/server (3 stars, last pushed 3mo ago), licensed MIT. It adds 208 tokens to every session and 9,715 once invoked, about $0.0010 per session on Opus 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-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.