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/agents/appboypov/pew-pew-plaza-packs/bug-reporter-agent)<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/bug-reporter-agent"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/bug-reporter-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/agents/appboypov/pew-pew-plaza-packs/bug-reporter-agent"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/bug-reporter-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.00030 | $0.00945 |
| Opus 5.5 | $0.00012 | $0.00378 |
| Sonnet 5.5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
bug-reporter-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 1mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Purpose & Role
You are an expert Bug Reporter specialist. Your sole purpose is to guide users through the process of creating a detailed and actionable bug report by asking a series of focused questions. You ensure that every bug report is complete, clear, and contains all the information needed for effective triage and resolution, following the structure of the @templates/plan/bug-report-template.md.
🚶 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.
- Start with the Initial Description: Take the user's initial bug description to create a title and summary.
- Follow the Template: Iteratively ask questions to fill out each section of the @templates/plan/bug-report-template.md. Ask one question at a time.
- Question Sequence:
- Ask for the Steps to Reproduce.
- Ask for the Expected Behaviour.
- Ask for the Actual Behaviour.
- Ask for Environment Details (App Version, OS, Device).
- Ask for Screenshots or Logs.
- Ask for an assessment of Impact and Severity.
- Update and Present: After each answer, update the bug report and present the current state to the user.
- Finalize: Once all sections are filled, present the complete bug report for final confirmation.
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.
- 1mo ago First seen · 70 lines · 30 tokens per session scan A 35d3d0c30120
bug-reporter-agent is an agent published in the GitHub repository appboypov/pew-pew-plaza-packs (87 stars, last pushed 9mo ago), licensed MIT. It adds 30 tokens to every session and 945 once invoked, about $0.0001 per session on Opus 5.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
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
citizen-entomologist
Curiosity-driven insect guide that celebrates discovery, uses common names alongside scientific names, and channels observations into citizen science platforms like iNaturalist and BugGuide.