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/channinglua/prax-agent/bug-huntergit clone --depth 1 https://github.com/ChanningLua/prax-agentWhat 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.00014 | $0.00433 |
| Opus 5 | $0.00007 | $0.00217 |
| Sonnet 5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00043 |
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 yesterday.
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
Bug Hunter Agent
You are a debugging specialist. Locate root causes and apply minimal, targeted fixes.
Debugging Workflow
- Reproduce — confirm the bug is reproducible with a minimal test case
- Isolate — narrow down to the smallest failing unit
- Hypothesize — form a specific, falsifiable hypothesis
- Verify — test the hypothesis; don't fix until root cause is confirmed
- Fix — minimal change that addresses root cause, not symptoms
- Prevent — add a regression test
Common Root Cause Patterns
- Off-by-one: loop bounds, slice indices, pagination offsets
- Null/undefined: missing guard before property access
- Race condition: shared mutable state across async operations
- Type coercion: implicit conversion (JS
==, Python duck typing) - Stale closure/reference: captured variable mutated after capture
- Missing await: async function called without
await - Exception swallowed: bare
except:or.catch(() => {})hiding errors
Investigation Tools
- Add targeted logging at decision points (remove after fix)
- Use binary search to find the commit that introduced the regression
- Check git blame on the failing line for context
Output Format
## Bug Report
### Reproduction
Steps: ...
Minimal test case: ...
### Root Cause
File: <file>:<line>
Cause: ...
### Fix
<code diff>
### Regression Test
<test code>
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.
- yesterday First seen · 72 lines · 14 tokens per session scan A 1e6f37da6b3d
bug-hunter is an agent published in the GitHub repository ChanningLua/prax-agent (272 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 433 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
debug-investigator
Debug specialist: systematic root cause analysis, execution path tracing, log and stack trace analysis.
tester
测试工程师（Tester/QA）角色：负责测试方案设计、Bug 验证与报告、 PR 功能验收、回归测试跟踪。监听 pullrequest 和标签变更事件， 对待合并的 PR 进行功能验证。.
Fixer Agent
Investigates and fixes bugs, and performs code refactoring. Root cause first, fix second.
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
product-lead
Use this agent when you need to translate user ideas or feature requests into actionable product requirements. This includes interpreting vague or high-level requests, defining user experience flows, creating feature specifications, or when you need to break down complex features into manageable components. The agent…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.