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 commands/aidemd-mcp/server/fixgit clone --depth 1 https://github.com/aidemd-mcp/serverWhat 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.00000 | $0.00406 |
| Opus 5 | $0.00000 | $0.00203 |
| Sonnet 5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
fix 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 yesterday.
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.
What it actually says
/aide:fix — Fix Phase
Agent: This command is executed by the
aide-implementoragent.
Work one unchecked item from the todo.aide checklist. This is the implementor phase in fix mode — the same agent that runs /aide:build, invoked with a narrower scope and a stricter one-session-per-item protocol. See todo.aide spec for the file format.
Checklist
- Read the intent spec (
.aideorintent.aide) in the target module - Read
todo.aideand pick the next unchecked item. Do not pick ahead, do not bundle. Read the item'sMisalignmenttag to understand where intent was lost - Fix exactly ONE issue. Do not fix adjacent issues discovered during the session — add them to the
todo.aidechecklist instead, unchecked, for future sessions - Base the fix on the spec, not on the one-line issue description. The description points at the problem; the spec is the source of truth for what correct looks like
- Run the generation command (or equivalent) to produce fresh output after the fix
- Compare the new output against the baseline from before the fix:
- Is the targeted issue resolved?
- Did anything else regress? The fix may have moved unrelated output further from the spec
- Run tests and the type checker to catch structural regressions
- Check the item off in
todo.aideonly if both the targeted fix landed and no regression was introduced. Otherwise revert, leave the item unchecked, and end the session - Commit the fix in its own commit — one checkbox, one commit, one diff
- End the session. The next item starts in a fresh session with clean context — do not continue working additional items in the same session
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.
- yesterday First seen · 21 lines · 0 tokens per session scan A 38834e0a64e5
fix is a command published in the GitHub repository aidemd-mcp/server (3 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 406 tokens. 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 commands, from other repositories
constitution
根据交互输入或已提供原则创建或更新项目章程，并确保相关模板保持同步。.
meta-theory-verify
Run the appropriate MetaKim verification path.
cross-research
Two-phase multi-model research. Phase A fans codex+gemini in parallel (benchmarks + citations angles); Phase B synthesises via fresh Claude session. Usage: /cross-research [--with | list | compare].
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
memory-why
Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.
ijfw-execute
Jump directly to the IJFW workflow Execute phase (Deep D4 / Quick Q3). Usage: /ijfw-execute [task or phase name].