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/workflow-acceptance-criteria-block)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/workflow-acceptance-criteria-block"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/workflow-acceptance-criteria-block/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/workflow-acceptance-criteria-block"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/workflow-acceptance-criteria-block.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.00027 | $0.00186 |
| Opus 5 | $0.00014 | $0.00093 |
| Sonnet 5 | $0.00005 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
workflow-acceptance-criteria-block 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.
What it actually says
Block Command
When this command is used, use the following block. Acknowledge your understanding and then await the user's request.
### Acceptance Criteria
> 💡 *Specific, measurable conditions that must be met for this phase/step to be considered successful.*
[List the checkable conditions that confirm completion and quality]
```
<example>
- [ ] [Specific condition that can be verified]
- [ ] [Quality metric that must be met]
- [ ] [Performance threshold that must be achieved]
- [ ] [Stakeholder approval or sign-off obtained]
- [ ] [Compliance or security requirement satisfied]
- [ ] [Testing or validation completed successfully]
</example>
```
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 · 28 lines · 27 tokens per session scan A 269183f6bb0f
workflow-acceptance-criteria-block is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 27 tokens to every session and 186 once invoked, about $0.0001 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
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.
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.
web-checklist
A checklist command for testing a website after a Git merge. It records checklist items in a file so progress can be viewed and individual checks can be marked complete.
test-coverage
Analyze test coverage and generate missing tests to reach 80%+ coverage.
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.