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/scope-block)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/scope-block"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/scope-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/scope-block"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/scope-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.00000 | $0.00321 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
scope-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.
## 🗺️ Scope
> 💡 *Clearly define what is included and explicitly excluded to prevent scope creep.*
### ✅ In Scope (Prioritized Features/Requirements)
> 💡 *List the specific features, requirements, or deliverables planned for this release, prioritized using MoSCoW method.*
**Must-have**
[List essential features and requirements]
```
<example>
- [Description of must-have requirement]
- [Another essential requirement]
</example>
```
**Should-have**
[List important but not critical features]
```
<example>
- [Description of should-have requirement]
- [Another important requirement]
</example>
```
**Could-have**
[List desirable features if time permits]
```
<example>
- [Description of could-have requirement]
- [Another nice-to-have requirement]
</example>
```
**Won't-have (This Release)**
[List explicitly excluded features]
```
<example>
- [Description of excluded requirement]
- [Another deferred requirement]
</example>
```
### ❌ Out of Scope
> 💡 *Explicitly list features, functionalities, or requirements that are NOT included in this specific release.*
[List out of scope items]
```
<example>
- [Feature/requirement that is explicitly not included]
- [Another feature that is deferred to future release]
- [Third feature that is outside project boundaries]
</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 · 71 lines · 0 tokens per session scan A 60994c9120d2
scope-block 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 321 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.