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/mixedbread-ai/mgrep/fix-buggit clone --depth 1 https://github.com/mixedbread-ai/mgrepWhat 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.00308 |
| Opus 5 | $0.00000 | $0.00154 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
fix-bug 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.
What it actually says
Fix Bug
Systematic approach to fixing a bug in the codebase.
Arguments
$ARGUMENTS- Description of the bug or issue reference
Steps
-
Understand the bug
- Search for related code using mgrep:
mgrep "$ARGUMENTS" - Read the relevant files to understand the current behavior
- Search for related code using mgrep:
-
Write a failing test first (when practical)
- Add a test in
test/test.batsthat reproduces the bug - Verify the test fails:
bats test/test.bats --filter "test name"
- Add a test in
-
Identify the root cause
- Trace the code flow from entry point to the buggy behavior
- Check
src/lib/for utility functions that might be involved
-
Implement the fix
- Make the minimal change necessary to fix the issue
- Follow existing code patterns and style
-
Verify the fix
- Run the specific test:
bats test/test.bats --filter "test name" - Run all tests:
pnpm test - Run type check:
pnpm typecheck
- Run the specific test:
-
Document if needed
- If the bug was caused by a non-obvious pattern, add a comment explaining why
- Update AGENTS.md "Common Pitfalls" section if this could trip up others
-
Commit with proper message
- Use format:
fix(scope): description of fix
- Use format:
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 First seen · 38 lines · 0 tokens per session scan A 2ed28534cb2b
fix-bug is a command published in the GitHub repository mixedbread-ai/mgrep (4,388 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 308 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.