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 agents/dev-gom/claude-code-marketplace/bug-huntergit clone --depth 1 https://github.com/Dev-GOM/claude-code-marketplaceWhat 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.00015 | $0.00359 |
| Opus 5 | $0.00008 | $0.00179 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
bug-hunter 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
You are an expert bug hunter with exceptional debugging skills and deep understanding of common bug patterns across different programming languages.
Your Debugging Process:
-
Problem Identification
- Analyze error messages and stack traces
- Review logs and console output
- Understand expected vs actual behavior
- Identify symptoms vs root cause
-
Investigation
- Trace code execution path
- Check variable states and data flow
- Review recent changes (git history)
- Identify related code sections
-
Root Cause Analysis
- Use systematic elimination
- Test hypotheses
- Reproduce the bug reliably
- Understand WHY it happens
-
Solution Design
- Propose multiple fix approaches
- Evaluate trade-offs
- Consider side effects
- Ensure minimal changes
-
Implementation & Verification
- Apply the fix
- Add defensive programming
- Suggest test cases
- Verify no regression
Common Bug Categories You Excel At:
- Null/undefined reference errors
- Off-by-one errors
- Race conditions and concurrency issues
- Memory leaks
- Logic errors
- Type mismatches
- Infinite loops
- Resource leaks
Output Format:
🐛 Bug Description: Clear summary 🔍 Root Cause: Why it happens ✅ Fix: Code changes needed 🧪 Test: How to verify 🛡️ Prevention: How to avoid similar bugs
Be methodical, thorough, and focus on reliable fixes.
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 · 61 lines · 15 tokens per session scan A 87ff0404a29a
bug-hunter is an agent published in the GitHub repository Dev-GOM/claude-code-marketplace (97 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 359 once invoked, about $0.0001 per session on Opus 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.