mgrep is a command-line search tool that finds information by meaning across code, text, PDFs, and images, rather than matching only exact words. Developers and coding agents use it to index repositories and search local files or the web with natural-language queries. Its catalogue entries add commands, skills, instructions, and a plugin for integrating mgrep into agent workflows.
Borrowing it
Nothing to install: this file belongs to mixedbread-ai/mgrep. 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/mixedbread-ai/mgrep/main/.claude/commands/fix-bug.mdgit clone --depth 1 https://github.com/mixedbread-ai/mgrepWrote 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/mixedbread-ai/mgrep/fix-bug)<a href="https://agentmods.dev/commands/mixedbread-ai/mgrep/fix-bug"><img src="https://agentmods.dev/badge/commands/mixedbread-ai/mgrep/fix-bug/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/mixedbread-ai/mgrep/fix-bug"><img src="https://agentmods.dev/badge/commands/mixedbread-ai/mgrep/fix-bug.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.00308 |
| Opus 5.5 | $0.00000 | $0.00123 |
| Sonnet 5.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 2mo 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.
- 2mo 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,426 stars, last pushed 6mo 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.