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/commands/aide/fix.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/commands/aidemd-mcp/server/fix)<a href="https://agentmods.dev/commands/aidemd-mcp/server/fix"><img src="https://agentmods.dev/badge/commands/aidemd-mcp/server/fix/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/commands/aidemd-mcp/server/fix"><img src="https://agentmods.dev/badge/commands/aidemd-mcp/server/fix.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.00000 | $0.00535 |
| Opus 5.5 | $0.00000 | $0.00214 |
| Sonnet 5.5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
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 4d 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 — 24 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/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.
The fix loop is autonomous: the orchestrator triages the todo list and approves it itself; the user never reviews it. Items tagged plan-gap or strategy-gap reach you only after the architect has amended the plan, and spec-gap items go to the spec writer, not to you. If an item still needs a design decision the plan does not make, do not invent one — leave it unchecked and report it back.
Checklist
- Read the todo list's status with
aide_frontmatter(read mode). Start only if it readsstatus: approved; otherwise stop and report back without changing anything - 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.
- 4d ago Changed · +3 lines 9fb4cb7df537
- 2mo ago First seen · 21 lines · 0 tokens per session scan A 38834e0a64e5
fix is a command published in the GitHub repository aidemd-mcp/server (4 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 535 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
watchdog
Run a superskill watchdog pass. Input: $ARGUMENTS (empty = dig the latest session).
api-aqa-flow-test-correction
Phase 7 Test Corrections of api-aqa-flow (USER APPROVAL REQUIRED).
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
ui-aqa-flow-test-correction
Phase 8 Test Correction of ui-aqa-flow.
doctor
Run IJFW health check (files, MCP server, hooks, memory, caps, framing).