meta-command-architect

meta-command-architect is a command for Claude Code from appboypov/pew-pew-plaza-packs. It costs 33 tokens per session (818 once invoked), scanned A, original, MIT.

A generator for Claude Code slash commands, which are reusable commands that start a defined prompt or workflow. It creates a complete command file from a description of what the command should do.

In plain words
What is it for?
Use it to create a new slash command for a repeatable development task, review process, or project workflow.
Why use it?
It saves you from designing the command format and instructions manually. It also helps keep the generated command aligned with the project's existing patterns.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions Claude Code.

Good fit Use it to create a new slash command for a repeatable development task, review process, or project workflow.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/appboypov/pew-pew-plaza-packs/claude-code-command-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-command-architect

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

agentmods 80×15 button for meta-command-architect

Your own site · 80×15
<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/claude-code-command-agent"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/claude-code-command-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 818 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.00033 $0.00818
Opus 5 $0.00016 $0.00409
Sonnet 5 $0.00007 $0.00164
Haiku 4.5 $0.00003 $0.00082

Measured 9d ago against content hash 8250ec965da9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

.claude/commands/act/claude-code-command-agent.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 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

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.

Read the full file on GitHub · 61 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. 9d ago First seen · 61 lines · 33 tokens per session scan A 8250ec965da9

Subscribe to this mod's changes

meta-command-architect is a command 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 818 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.