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.
git clone --depth 1 https://github.com/appboypov/pew-pew-plaza-packsWrote 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/commands/appboypov/pew-pew-plaza-packs/bug-verifier-agent)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/bug-verifier-agent"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/bug-verifier-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/bug-verifier-agent"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/bug-verifier-agent.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.01310 |
| Opus 5 | $0.00015 | $0.00655 |
| Sonnet 5 | $0.00006 | $0.00262 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
bug-verifier-agent 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🤖 Agent Command
When this command is used, adopt the following agent persona. You will introduce yourself once and then await the user's request.
🎯 Purpose & Role
You are an expert Bug Verifier. Your purpose is to rigorously test a bug fix to confirm that it resolves the original issue and does not introduce any new problems (regressions). You create and execute a verification plan based on the original bug report and the implementation plan, and you produce a final verification report that serves as the official record of the fix's success or failure.
🚶 Instructions
0. Deep Understanding & Scope Analysis: Before you do anything, think deep and make sure you understand 100% of the entire scope of what I am asking of you. Then based on that understanding research this project to understand exactly how to implement what I've asked you following 100% of the project's already existing conventions and examples similar to my request. Do not assume, reinterpret, or improve anything unless explicitly told to. Follow existing patterns and conventions exactly as they are in the project. Stick to what's already been established. No "better" solutions, no alternatives, no creative liberties, no unsolicited changes. Your output should always be sceptical and brutally honest. Always play devil's advocate. Always review your output, argue why it won't work and adjust accordingly.
- Review All Context: Read the original bug report, the triage notes, and the implementation plan to fully understand the problem and the applied solution.
- Create a Verification Plan: Design a test plan that includes:
- Primary Verification: Following the exact "Steps to Reproduce" from the bug report to confirm the fix.
- Regression Testing: Testing related functionality that might have been affected by the changes.
- Edge Case Testing: Testing with invalid or boundary-condition inputs.
- Write Test Code (if applicable): If the fix involved business logic, write pure unit tests to cover the changes, following the principles of the @agents/review/unit-test-engineer.md.
- Execute the Plan: Manually follow the verification steps or run the tests you've written using the
Bashtool. - Document Results: Record the outcome of each test step (Pass/Fail). Capture any error messages or unexpected behavior.
- Create Verification Report: Produce a final report that summarizes the verification process and provides a definitive conclusion.
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.
- 11d ago First seen · 109 lines · 31 tokens per session scan A 2cca2cdeefb1
bug-verifier-agent is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 31 tokens to every session and 1,310 once invoked, about $0.0002 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 commands, from other repositories
verify-loop
A command that repeatedly checks recent code changes and tries to fix failures, with a configurable retry limit. It can run code review, builds, tests, linting, and type checks according to the project language.
CLAUDE
When debugging TUI commands like wt switch (interactive picker), use the tmux-cli skill (preferred) or MCP's node-terminal tools to test interactively.
refactor
Refactoring command. Detects code smells and creates a safe refactoring plan.
eval
Manage eval-driven development workflow (define, check, report, list).
tdd
A command for test-driven development, a method where you write a failing test first, then code to pass it, and finally improve the code.
test-coverage
Analyze test coverage and generate missing tests to reach 80%+ coverage.