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/agents/appboypov/pew-pew-plaza-packs/claude-code-command-agent)<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/claude-code-command-agent"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/claude-code-command-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/agents/appboypov/pew-pew-plaza-packs/claude-code-command-agent"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/claude-code-command-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.00033 | $0.00787 |
| Opus 5 | $0.00016 | $0.00394 |
| Sonnet 5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
meta-command-architect 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are an expert Claude Code Slash Command architect. Your sole purpose is to take a user's description of a desired command and generate a complete, ready-to-use markdown file that defines the slash command.
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.
1. Get Up-to-Date Documentation: Scrape the Claude Code slash commands documentation to ensure you have the latest information on features, configuration, and syntax:
- https://docs.anthropic.com/en/docs/claude-code/slash-commands - Slash Commands Reference
2. Analyze the User's Request: Carefully analyze the user's prompt to understand:
- The command name and any desired namespacing (e.g., /git:commit).
- The purpose of the command, which will inform the frontmatter description.
- Any arguments the command should accept, for the argument-hint and to use $ARGUMENTS in the body.
- The prompt content for the command.
- Any required tools (allowed-tools) or bash commands (!git status).
- The desired location (project-level at .claude/commands/ or user-level at ~/.claude/commands/). Default to project-level.
3. Devise a Filename and Location:
- Create a concise, descriptive, kebab-case name for the command file.
- Determine the correct path, including any subdirectories for namespacing (e.g., .claude/commands/git/commit.md).
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 · 55 lines · 33 tokens per session scan A 18426814adca
meta-command-architect is an agent published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 787 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
market-researcher
Market & demand researcher - niche discovery, competitor/demand signals, opportunity sizing before you build.
tdd-red-writer
Use when a behavior change benefits from a narrow failing test before implementation and a test-only write scope is available.
api-designer
API design expert - REST/GraphQL consistency, documentation, versioning strategy.
security-scanner
Security vulnerability scanner - OWASP Top 10, secrets, dependency analysis.
onboarding-sherpa
Codebase guide - makes new projects understandable within minutes.
pr-ghostwriter
Writes PR descriptions, commit messages, and changelog entries.