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.
git clone --depth 1 https://github.com/AKSoftCode/aicrewWrote 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/aksoftcode/aicrew/fix)<a href="https://agentmods.dev/commands/aksoftcode/aicrew/fix"><img src="https://agentmods.dev/badge/commands/aksoftcode/aicrew/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/aksoftcode/aicrew/fix"><img src="https://agentmods.dev/badge/commands/aksoftcode/aicrew/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.00018 | $0.01834 |
| Opus 5.5 | $0.00007 | $0.00734 |
| Sonnet 5.5 | $0.00004 | $0.00367 |
| Haiku 4.5 | $0.00002 | $0.00183 |
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 1mo 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fast bug fix — 3 intake questions, then TDD straight to done. Use /dev instead for features, refactors, or anything needing a design spec.
Default output: caveman/lean — terse by default.
/normalor/lean offfor verbose. See~/Agents/agents/caveman.md.
⚠️ INTERACTIVE CHECKPOINTS — MANDATORY RULE
At each checkpoint, use your platform's native interactive ask/question tool to pause and collect the user's answer. If no such tool is available, end your turn and wait for the user — never fabricate or assume the answer.
Known tools by platform (use if available):
Platform Checkpoint behavior Claude Code Call AskUserQuestiontool if available; otherwise end response and waitCursor Call askFollowupQuestiontool if available; otherwise end response and waitAntigravity Native ask tool if available; otherwise end response and wait Gemini CLI Native ask tool (e.g. ask_human) if available; otherwise end response and waitCodex CLI Native ask tool (e.g. ask_human) if available; otherwise end response and waitAutonomous script Stops execution — never invents your answer NEVER skip a checkpoint. NEVER fabricate the user's response.
/fix — Fast Bug Fix
Streamlined entry point for bug fixes. Skips the full intake ceremony.
Use /dev instead if you need brainstorming, refactor planning, or a feature.
Auto-detect project context (silently)
ls .ai/team/roles/→ use team roles if availablels .ai/skills/agents/→ use project agents if available- Detect stack: pubspec.yaml / requirements.txt / package.json
- Read CLAUDE.md or AGENTS.md if present
INTAKE — 3 questions only
If $ARGUMENTS describes the bug clearly, use it and skip straight to question 3.
Otherwise ask all three at once:
Quick bug questions:
- What's the exact symptom or error message?
- Which file, endpoint, or screen?
- Steps to reproduce? (or "not sure" is fine)
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.
- 1mo ago First seen · 171 lines · 18 tokens per session scan A c0ae082de478
fix is a command published in the GitHub repository AKSoftCode/aicrew (3 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 1,834 once invoked, about $0.0001 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 commands, from other repositories
pair
AI pair programming — switch between Driver, Navigator, TDD, Review, and Debug modes.
bugfix
Quality bug-fix workflow for P1/P2 issues with full TDD cycle.
spec-impl
Execute spec tasks using TDD methodology.
validate-build
Validates project build process. Run after changes to ensure the project compiles/transpiles correctly.
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.