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/issue)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/issue"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/issue/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/issue"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/issue.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.00037 | $0.05376 |
| Opus 5 | $0.00018 | $0.02688 |
| Sonnet 5 | $0.00007 | $0.01075 |
| Haiku 4.5 | $0.00004 | $0.00538 |
Grade A, and why
create-issue 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 9d 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 — 664 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Command
When this command is used, check if any required information is missing. If so, ask the user to provide it. Otherwise, proceed with the request.
🛠️ Issue Workflow: Systematic Requirements Decomposition
💡 Transform vague technical requests into comprehensive, actionable issues through systematic decomposition and low cognitive load questioning that reveals all requirements naturally.
🎯 End Goal
💡 The measurable objective that determines whether any following section provides value. This is the north star for inclusion decisions.
Create a comprehensive technical issue document that:
- Defines a single clear outcome the system/user must achieve
- Identifies all atomic requirements and components without assumptions
- Documents properties, behaviors, deliverables, and checkpoints
- Provides accurate effort estimates based on complete understanding
- Follows MVP mindset focusing only on must-haves
- Maintains context rot awareness by including only value-adding information
Deliverables
- Complete tech issue document with all sections populated
- Clear end goal with measurable success criteria
- Atomic component breakdown with properties and behaviors
- Grouped deliverables as testable units
- Chronological checkpoints with acceptance criteria
- Realistic effort estimates with justification
Acceptance Criteria
- End goal is specific and measurable
- All requirements traced back to explicit user confirmation
- Components broken down to atomic level
- Properties and behaviors fully documented
- Deliverables grouped for parallel work
- Checkpoints enable progress tracking
- Effort estimates based on complete scope
👤 Persona
Role
Technical requirements analyst and systematic decomposer
Expertise
Requirements engineering, systematic questioning, component decomposition, effort estimation
Communication Style
Patient, methodical, uses low cognitive load questions, reveals information naturally
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.
- 9d ago First seen · 664 lines · 37 tokens per session scan A ca0fb2b1624f
create-issue is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 37 tokens to every session and 5,376 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-09-03.
Other commands, from other repositories
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
plan-ceo-review
Strategic product gate — challenge the brief, find the 10-star product hiding inside the request, before writing any code.
team
Virtual eng team orchestrator. Runs a goal end-to-end through the whole team — strategy → plan → build → QA → ship — conducted by the engineering-manager, delegating to every specialist. One entry point that connects /ceo-review, /eng-review, /qa, and /ship.
content-start
Content production session start command. Gives the daily content session a structured start, shows pending work, and sets priorities.
proposal
Client proposal command. Builds a professional client proposal from project summaries. Valid for 30 days.
dashboard
Daily statistics panel. Presents task, audit, event, and performance data as a unified table.