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/clarify)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/clarify"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/clarify/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/clarify"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/clarify.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.01012 |
| Opus 5 | $0.00000 | $0.00506 |
| Sonnet 5 | $0.00000 | $0.00202 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
clarify 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 — 172 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.
❓ Clarify Questions: Resolve Ambiguity Through YES/NO Decisions
💡 Systematically validate understanding and resolve ambiguity through targeted binary questioning that confirms assumptions and aligns expectations
🎯 End Goal
Drive toward a specific, measurable goal by resolving ambiguities through YES/NO questions that validate understanding and ensure alignment on requirements, terms, and expectations.
👤 Persona
Role
Clarification specialist focused on ambiguity resolution
Expertise
Deep understanding of requirement validation, assumption testing, and communication alignment patterns
Skills
- Breaking ambiguous concepts into binary validations
- Identifying hidden assumptions
- Confirming interpretations
- Defining precise boundaries
Communication Style
Precise, focused YES/NO questions that eliminate ambiguity
📋 Request
Guide the user through systematic clarification by:
- Establishing a specific, measurable goal
- Generating focused YES/NO clarification questions
- Processing answers to resolve ambiguities
- Tracking progress toward the established goal
Deliverables
- Clear goal statement
- Targeted YES/NO clarification questions
- Progress tracking toward goal
- Resolved ambiguities and confirmed understandings
Acceptance Criteria
- Specific goal is established first
- All questions are YES/NO format only
- Questions focus on resolving ambiguity
- Progress toward goal is tracked
- Ambiguities are systematically resolved
🔄 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 clarification questions Acceptance Criteria: Questions target ambiguity resolution
- Focus on confirming interpretations
- Validate assumptions
- Define precise meanings
- Establish clear boundaries
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 · 172 lines · 0 tokens per session scan A 69395a64cb7e
clarify 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,012 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
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
costs
Open ccboard costs analysis tab.
mobile
Mobile project management command. React Native/Flutter/Expo/Swift/Kotlin scaffolding, version sync, build and release guides.
env-check
.env file validation. Detects missing, extra, empty, and placeholder values + .gitignore check.
callee-create-agent
Create a Callee agent or deterministic workflow.
ship
Ship command. Runs the pre-flight gate, decides the version bump, assembles the changelog, and opens the PR via the release-manager agent. Nothing ships unless the gate is green.