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/prompt-rules)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/prompt-rules"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/prompt-rules/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/prompt-rules"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/prompt-rules.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.00019 | $0.01466 |
| Opus 5 | $0.00010 | $0.00733 |
| Sonnet 5 | $0.00004 | $0.00293 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade A, and why
prompt-rules 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instruction Command
When this command is used, acknowledge that you understand these instructions and will follow them throughout the conversation. Then await the user's request.
📏 Prompt Rules
💡 Absolute requirements and prohibitions for creating prompts that follow the modular philosophy.
👍 Always Rules
WHEN creating any prompt
- ALWAYS start with defining the End Goal first
- ALWAYS include both End Goal and Request sections (minimum required)
- ALWAYS follow the exact structure from @templates/meta/prompt-template.md
- ALWAYS use verb-subject naming pattern for files
- ALWAYS include YAML frontmatter with name and description
WHEN defining the End Goal
- ALWAYS make it specific and measurable
- ALWAYS write it as an outcome, not a process
- ALWAYS keep it concise but complete
- ALWAYS use it as the filter for all other sections
- ALWAYS ensure success can be clearly determined
WHEN adding optional sections
- ALWAYS verify each section contributes to the End Goal
- ALWAYS document why the section is included (in comments if needed)
- ALWAYS test if the prompt would fail without the section
- ALWAYS exclude sections that don't pass the contribution test
- ALWAYS prefer exclusion when value is uncertain
WHEN structuring the Request section
- ALWAYS start with a verb (Create, Update, Analyze, Transform, etc.)
- ALWAYS specify the complete scope of work
- ALWAYS include deliverables if specific outputs are required
- ALWAYS add acceptance criteria if success needs validation
- ALWAYS keep the main request concise and clear
WHEN creating Workflow sections
- ALWAYS make steps atomic and testable
- ALWAYS include deliverables for each step
- ALWAYS specify acceptance criteria per step
- ALWAYS use descriptive step names
- ALWAYS number steps sequentially
WHEN writing Instructions sections
- ALWAYS use the WHEN/THEN event pattern
- ALWAYS group by scenario or context
- ALWAYS include only rules that prevent failure
- ALWAYS make instructions actionable and specific
- ALWAYS avoid redundancy with other sections
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 · 197 lines · 19 tokens per session scan A ceb171bbe0c3
prompt-rules is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 19 tokens to every session and 1,466 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
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.
content-idea
Content idea generation command. Creates a structured idea list for a topic, theme, or platform.
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.