meta-feature-agent

meta-feature-agent is a command for Claude Code from appboypov/pew-pew-plaza-packs. It costs 53 tokens per session (12,103 once invoked), scanned A, original, MIT.

An autonomous process for handling all six stages of a feature workflow, from the initial request to implementation plans. It performs the stages itself instead of handing them to other agents.

In plain words
What is it for?
Use it when you want one process to investigate a feature, create planning documents, analyze the workflow, and produce implementation plans.
Why use it?
It removes the need to coordinate each planning stage manually. It also applies project conventions while analyzing and refining the work.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

Good fit Use it when you want one process to investigate a feature, create planning documents, analyze the workflow, and produce implementation plans.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/appboypov/pew-pew-plaza-packs/meta-feature-agent
Install

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.

Clone the repo
git clone --depth 1 https://github.com/appboypov/pew-pew-plaza-packs

Made for: Claude Code.

Wrote 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.

agentmods badge for meta-feature-agent

README.md
[![agentmods](https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/meta-feature-agent/github.svg)](https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/meta-feature-agent)
Your own site
<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/meta-feature-agent"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/meta-feature-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.

agentmods 80×15 button for meta-feature-agent

Your own site · 80×15
<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/meta-feature-agent"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/meta-feature-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 12,103 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.12103
Opus 5 $0.00026 $0.06051
Sonnet 5 $0.00011 $0.02421
Haiku 4.5 $0.00005 $0.01210

Measured 13d ago against content hash 5df07b582ec1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

meta-feature-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 13d 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.

Origin

Copies of this mod

5 near-identical copies found in the catalogue:

.claude/commands/act/meta-feature-agent.md · 1,317 lines

How it starts

The opening of the file, as written. The whole thing — 1,317 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 the ultimate meta-level feature workflow expert, combining the sophisticated analytical capabilities of a meta-agent with comprehensive knowledge of the 6-phase feature development workflow. You don't just orchestrate—you understand, analyze, optimize, and autonomously execute the entire workflow from initial request to implementation plans. You NEVER delegate to other agents; instead, you embody each phase agent's expertise by studying their personas and taking on their roles directly. Your expertise spans both the theoretical foundations of progressive refinement and the practical execution of each phase, enabling you to adapt the workflow to any scenario while maintaining systematic coverage and quality.

🚶 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

Read the full file on GitHub · 1,317 lines

Changes

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.

  1. 13d ago First seen · 1,317 lines · 53 tokens per session scan A 5df07b582ec1

Subscribe to this mod's changes

meta-feature-agent is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 53 tokens to every session and 12,103 once invoked, about $0.0003 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.