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/meta-issue-agent)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/meta-issue-agent"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/meta-issue-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/meta-issue-agent"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/meta-issue-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.00054 | $0.11068 |
| Opus 5.5 | $0.00022 | $0.04427 |
| Sonnet 5.5 | $0.00011 | $0.02214 |
| Haiku 4.5 | $0.00005 | $0.01107 |
Grade A, and why
meta-issue-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.
This is a copy
81% identical to meta-feature-agent — 508 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,183 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 Issue Management Architect specializing in creating, transforming, and updating structured issues across all business domains. You understand the distinct patterns for technical, operational, marketing, sales, financial, and people-related issues. Your expertise lies in analyzing requirements to determine the appropriate issue type, applying domain-specific templates, and ensuring issues are actionable, measurable, and properly structured for implementation.
🚶 Instructions
📐 Project Conventions
💡 Project-specific conventions and standards that maintain consistency across the codebase must be adhered to at all times.
💡 Concept: Pew Pew Philosophy
💡 The modular approach to good prompts and agents.
💡 Concept: A Good Prompt
💡 A clear and concise description of what makes a good prompt in this framework.
📝 A Good Prompt
The foundation of this framework is understanding what makes an effective prompt. Every prompt consists of modular components, each included only when it contributes to achieving the end goal.
Claude Commands: /plx:create (new), /plx:update (enhance), /plx:make (transform)
graph TD
EG[🎯 End Goal<br/>Achievement Objective]
P[👤 Persona<br/>Optional Expertise]
R[📋 Request<br/>Verb-First Activity]
W[🔄 Workflow<br/>Optional Steps]
I[📏 Instructions<br/>Optional Rules]
O[📊 Output Format<br/>Optional Structure]
EG --> P
EG --> R
EG --> W
EG --> I
EG --> O
P -.->|Contributes to| EG
R -.->|Required for| EG
W -.->|Enhances| EG
I -.->|Guides toward| EG
O -.->|Structures| EG
style EG fill:#663399,stroke:#fff,stroke-width:4px,color:#fff
style R fill:#2e5090,stroke:#fff,stroke-width:2px,color:#fff
style P fill:#4a5568,stroke:#fff,stroke-width:2px,color:#fff
style W fill:#4a5568,stroke:#fff,stroke-width:2px,color:#fff
style I fill:#4a5568,stroke:#fff,stroke-width:2px,color:#fff
style O fill:#4a5568,stroke:#fff,stroke-width:2px,color:#fff
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 · 1,183 lines · 54 tokens per session scan A 3116e30f66a6
meta-issue-agent is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (87 stars, last pushed 9mo ago), licensed MIT. It adds 54 tokens to every session and 11,068 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to meta-feature-agent, differing in 508 lines, and is treated as a copy.
Other commands, from other repositories
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.
create-plan
Writes an implementation plan as a file artifact in the task directory (.ork/tasks/TASK/NN-plan-SLUG.md) with phases, exact file changes and runnable success criteria, so reviewers comment on the file instead of in chat. Use when a task has its research done and needs a reviewable plan before code; pair with…