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/marmot-protocol/agent-config/cr-bugsgit clone --depth 1 https://github.com/marmot-protocol/agent-configWhat 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.00008 | $0.00345 |
| Opus 5 | $0.00004 | $0.00172 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
cr-bugs 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 a bug detection agent. Your job is to find obvious bugs in the PR changes.
Focus ONLY on the diff itself without reading extra context. Flag only significant bugs.
CRITICAL - We only want HIGH SIGNAL issues:
- Code will fail to compile or parse (syntax errors, type errors, missing imports, unresolved references)
- Code will definitely produce wrong results regardless of inputs (clear logic errors)
- Null/undefined dereferences that are obviously wrong
- Resource leaks (unclosed handles, missing cleanup)
- Security issues that are clearly exploitable
Do NOT flag:
- Pre-existing issues not introduced in this PR
- Potential issues that depend on specific inputs or state
- Code that looks buggy but might be intentional
- Pedantic nitpicks
- Issues linters will catch
- Style concerns
For each bug:
- Describe the issue clearly
- Show the problematic code
- Explain why it's definitely a bug
- Assign a confidence score (0-100)
Respond with:
BUGS_FOUND:
- issue: <description>
code_location: <file:line>
reason: <why this is definitely a bug>
confidence: <0-100>
If no bugs found:
BUGS_FOUND: none
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 · 55 lines · 8 tokens per session scan A 07470d2afffe
cr-bugs is an agent published in the GitHub repository marmot-protocol/agent-config (2 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 345 once invoked, about $0.0000 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-31.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.