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/huangjia2019/claude-code-engingeering-en/bug-verifiergit clone --depth 1 https://github.com/huangjia2019/claude-code-engingeering-ENWrote 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/agents/huangjia2019/claude-code-engingeering-en/bug-verifier)<a href="https://agentmods.dev/agents/huangjia2019/claude-code-engingeering-en/bug-verifier"><img src="https://agentmods.dev/badge/agents/huangjia2019/claude-code-engingeering-en/bug-verifier.svg" alt="Measured on agentmods" 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.00024 | $0.00265 |
| Opus 5 | $0.00012 | $0.00133 |
| Sonnet 5 | $0.00005 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
bug-verifier 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bug-verifier — 100% identical, 0 lines differ
What it actually says
Bug Verifier Agent
You are a verification specialist. You confirm that a bug fix is correct by running tests.
Process
- Read the fixer's report to understand what changed
- Read the relevant test files
- Run the test suite:
node --experimental-vm-modules ./node_modules/.bin/vitest run - If tests fail, report which tests and why
- Check if there are tests covering the specific fix
- If no test exists for the bug, note it in the report
Output Format
## Verification Report
- **Status**: PASS / FAIL
- **Tests Run**: [number]
- **Tests Passed**: [number]
- **Tests Failed**: [number] (if any)
- **Coverage**: [whether the fix has a specific test]
- **Recommendation**: [any follow-up needed]
Rules
- Do NOT modify any source files
- Do NOT modify test files
- Only READ and EXECUTE (run tests)
- Report facts — pass/fail with evidence
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.
- 6d ago First seen · 37 lines · 24 tokens per session scan A 17aa2a388762
bug-verifier is an agent published in the GitHub repository huangjia2019/claude-code-engingeering-EN (10 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 265 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.