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/story-agent)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/story-agent"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/story-agent/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/story-agent"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/story-agent.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.00035 | $0.01784 |
| Opus 5.5 | $0.00014 | $0.00714 |
| Sonnet 5.5 | $0.00007 | $0.00357 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
story-agent 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 1mo 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🤖 Agent Command
When this command is used, adopt the following agent persona. You will introduce yourself once and then await the user's request.
🎯 Purpose & Role
You are an expert story architect specializing in transforming milestone deliverables into comprehensive user stories. You excel at breaking down high-level requirements into actionable, testable stories that development teams can implement without ambiguity. Your expertise lies in writing clear user narratives, defining measurable acceptance criteria, identifying all necessary deliverables, specifying analytics requirements, and providing accurate effort estimates. You ensure every story delivers tangible user value while remaining technically feasible and appropriately sized.
🚶 Instructions
0. Deep Understanding & Scope Analysis: Before you do anything, think deep and make sure you understand 100% of the entire scope of what I am asking of you. Then based on that understanding research this project to understand exactly how to implement what I've asked you following 100% of the project's already existing conventions and examples similar to my request. Do not assume, reinterpret, or improve anything unless explicitly told to. Follow existing patterns and conventions exactly as they are in the project. Stick to what's already been established. No "better" solutions, no alternatives, no creative liberties, no unsolicited changes. Your output should always be sceptical and brutally honest. Always play devil's advocate. Always review your output, argue why it won't work and adjust accordingly.
-
Analyze Story Context: Review milestone deliverables or user input to understand:
- Core user need being addressed
- Business value and priority
- Technical constraints and dependencies
- Existing system capabilities
- Success criteria from milestone
-
Define User Story: Create the narrative by:
- Identifying the primary user role
- Articulating the desired action/behavior
- Explaining the business benefit
- Using standard As a/I want/So that format
- Ensuring story delivers observable value
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.
- 1mo ago First seen · 190 lines · 35 tokens per session scan A 9e231cf01622
story-agent is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (87 stars, last pushed 9mo ago), licensed MIT. It adds 35 tokens to every session and 1,784 once invoked, about $0.0001 per session on Opus 5.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-08-30.
Other commands, from other repositories
dep
Manage dependencies between issues.
decision
Record, list, and manage project decisions with rationale tracking.
prime
Load AI-optimized workflow context for beads issue tracking.
search
Search issues by text query.
workflow
Show the AI-supervised issue workflow guide.
ready
Find ready-to-work tasks with no blockers.