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/agent-rules)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/agent-rules"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/agent-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/agent-rules"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/agent-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.01230 |
| Opus 5 | $0.00010 | $0.00615 |
| Sonnet 5 | $0.00004 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
agent-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 — 191 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.
📏 Agent Rules
💡 Non-negotiable rules that ensure agent quality, security, and consistency.
👍 Always
WHEN creating new agents
- ALWAYS include all required sections from @templates/agents/agent-template.md
- ALWAYS start with single, focused purpose
- ALWAYS include YAML frontmatter with name, description, and color
- ALWAYS verify all wikilinks resolve to actual files
- ALWAYS follow kebab-case naming convention
- ALWAYS place agents in appropriate subdirectory
WHEN writing agent descriptions
- ALWAYS include expertise statement first
- ALWAYS use "Use when..." pattern for delegation
- ALWAYS wrap description in double quotes
- ALWAYS keep descriptions action-oriented
- ALWAYS make delegation triggers specific
WHEN structuring agent content
- ALWAYS include instruction 0 for scope analysis
- ALWAYS use exact section headers and emojis from template
- ALWAYS maintain section order from template
- ALWAYS provide clear output format specification
- ALWAYS include quality standards table
WHEN defining tool access
- ALWAYS consider security implications
- ALWAYS document tool requirements in Purpose section
- ALWAYS apply principle of least privilege
- ALWAYS justify any broad tool access
- ALWAYS review MCP tool implications
WHEN using wikilinks
- ALWAYS verify referenced files exist
- ALWAYS place embedded wikilinks on separate lines
- ALWAYS use standard wikilink format without backticks
- ALWAYS end example wikilinks with "-wl-example"
- ALWAYS check for circular dependencies
WHEN writing instructions
- ALWAYS make instructions actionable and specific
- ALWAYS use numbered format starting with 0
- ALWAYS bold action names in instructions
- ALWAYS include error handling guidance
- ALWAYS provide success criteria
WHEN documenting context
- ALWAYS include Project Files & Code section
- ALWAYS include Documentation & External Resources section
- ALWAYS provide relevance notes for each reference
- ALWAYS organize references by category
- ALWAYS verify external links are accessible
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 · 191 lines · 19 tokens per session scan A bff3b1838384
agent-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,230 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.
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.