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/meta-issue-agent)<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/meta-issue-agent"><img src="https://agentmods.dev/badge/agents/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/agents/appboypov/pew-pew-plaza-packs/meta-issue-agent"><img src="https://agentmods.dev/badge/agents/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.11037 |
| Opus 5.5 | $0.00022 | $0.04415 |
| Sonnet 5.5 | $0.00011 | $0.02207 |
| Haiku 4.5 | $0.00005 | $0.01104 |
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
86% identical to makefile-expert — 320 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,177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 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,177 lines · 54 tokens per session scan A c91943a9387a
meta-issue-agent is an agent 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,037 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to makefile-expert, differing in 320 lines, and is treated as a copy.
Other agents, from other repositories
gem-planner
Create lean, decision-complete wave plans with clear task ownership, outputs, and validation.
react18-commander
Master orchestrator for React 16/17 → 18.3.1 migration. Designed for class-component-heavy codebases. Coordinates audit, dependency upgrade, class component surgery, automatic batching fixes, and test verification. Uses memory to gate each phase and resume interrupted sessions. 18.3.1 is the target - it…
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
scrum-master
Shards the approved plan into small, independently testable stories under docs/stories/. Use once the owner has approved the plan.
aiox-pm
AIOX Project Manager autônomo. Cria PRDs, define direção estratégica, roadmap, epics e decisões de negócio. Usa task files reais do AIOX.
linear
Linear bookkeeping for one unit of work in a repo with a Linear mapping: find or create its issue, move the status with the work, keep its checklist and progress comments current, and file follow-up issues. Spawn at each milestone: work started, PR opened, CI result, merged, work deferred. RETURNS: the issue ID and…