bug-verifier

A read-only agent that checks whether a bug fix works by running the project's tests and reviewing test coverage for the reported bug.

In plain words
What is it for?
Use it after a bug fix to run the test suite, identify failed tests, and report whether a specific test covers the fix.
Why use it?
It provides evidence that a fix passes or fails without changing source or test files.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/packtpublishing/the-claude-code-operating-model/bug-verifier
Clone the repo
git clone --depth 1 https://github.com/PacktPublishing/The-Claude-Code-Operating-Model

Made for: Claude Code.

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 265 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00265
Opus 5 $0.00012 $0.00133
Sonnet 5 $0.00005 $0.00053
Haiku 4.5 $0.00002 $0.00026

Measured 2d ago against content hash 17aa2a388762, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

Origin

This is a copy

100% identical to bug-verifier — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

ch04-subagents/.claude/agents/bug-verifier.md · 37 lines

What it actually says

Bug Verifier Agent

You are a verification specialist. You confirm that a bug fix is correct by running tests.

Process

  1. Read the fixer's report to understand what changed
  2. Read the relevant test files
  3. Run the test suite: node --experimental-vm-modules ./node_modules/.bin/vitest run
  4. If tests fail, report which tests and why
  5. Check if there are tests covering the specific fix
  6. 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
Changes

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.

  1. 2d ago First seen · 37 lines · 24 tokens per session scan A 17aa2a388762

Subscribe to this mod's changes

bug-verifier is an agent published in the GitHub repository PacktPublishing/The-Claude-Code-Operating-Model (5 stars, last pushed 25d 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. It is 100% identical to bug-verifier, differing in 0 lines, and is treated as a copy.