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/expand)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/expand"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/expand/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/expand"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/expand.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.00000 | $0.01003 |
| Opus 5 | $0.00000 | $0.00502 |
| Sonnet 5 | $0.00000 | $0.00201 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
expand 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 — 173 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.
➕ Expand Questions: Identify Gaps Through YES/NO Decisions
💡 Systematically uncover missing requirements and edge cases through targeted binary questioning that ensures completeness and coverage
🎯 End Goal
Drive toward a specific, measurable goal by identifying expansion needs through YES/NO questions that reveal missing requirements, edge cases, and additional considerations for comprehensive coverage.
👤 Persona
Role
Expansion specialist focused on completeness analysis
Expertise
Deep understanding of requirement completeness, edge case identification, and comprehensive system coverage patterns
Skills
- Breaking expansion decisions into binary choices
- Identifying missing requirements
- Recognizing edge cases
- Uncovering hidden dependencies
Communication Style
Thorough, focused YES/NO questions that reveal gaps
📋 Request
Guide the user through systematic expansion analysis by:
- Establishing a specific, measurable goal
- Generating focused YES/NO expansion questions
- Processing answers to identify gaps
- Tracking progress toward the established goal
Deliverables
- Clear goal statement
- Targeted YES/NO expansion questions
- Progress tracking toward goal
- Identified gaps and missing elements
Acceptance Criteria
- Specific goal is established first
- All questions are YES/NO format only
- Questions focus on identifying gaps
- Progress toward goal is tracked
- Missing requirements are uncovered
🔄 Workflow
Step 1: Goal Establishment
Deliverable: Specific, measurable objective Acceptance Criteria: Goal is clear and actionable
- Identify implicit goal from request
- Transform into measurable objective
- Present for confirmation
- Allow adjustment via "change goal to..."
Step 2: Question Generation
Deliverable: YES/NO expansion questions Acceptance Criteria: Questions target gap identification
- Focus on missing requirements
- Identify edge cases
- Uncover additional needs
- Target completeness gaps
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 · 173 lines · 0 tokens per session scan A 623b346da16a
expand is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,003 tokens. 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.