Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add nguyenthienthanh/aura-frog/plugin install aura-frogWrote 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/nguyenthienthanh/aura-frog/plan-expand)<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/plan-expand"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/plan-expand.svg" alt="Measured on agentmods" 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.00000 | $0.00322 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
plan-expand 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 6d 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.
What it actually says
/aura-frog:plan-expand <id>
Decompose a plan node one tier down (T1→T2, T2→T3, T3→T4). Alias for /aura-frog:plan expand <id> (v3.7.2+).
Usage
/aura-frog:plan-expand FEAT-A # decompose Feature into Stories
/aura-frog:plan-expand STORY-0042 # decompose Story into Tasks
/aura-frog:plan-expand INIT-001 # decompose Initiative into Features
Delegation
This file is a thin alias. Claude MUST translate the invocation to:
bash aura-frog/scripts/plans/expand-node.sh <ID> [--dry-run] [--plans-dir <path>]
Then dispatch the appropriate agent (feature-architect for T1→T2, story-planner for T2→T3 or T3→T4) to write the child node files using the prepared checkpoint and counter. Full protocol in commands/plan.md and skills/plan-orchestrator/SKILL.md.
Why an alias?
Backwards-compatible from pre-v3.7.2 — old muscle memory still works. New users should prefer /aura-frog:plan expand <id> (consolidated form).
Deprecation timeline: soft-deprecated v3.7.2, warning v4.0, removed v5.0.
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.
- 6d ago First seen · 30 lines · 0 tokens per session scan A 86fcde126d10
plan-expand is a command published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 322 tokens. 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 commands, from other repositories
review-agentready
AgentReady-specific code review with attribute mapping and score impact analysis.
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
resume_handoff
Resume work from handoff document with context analysis and validation.
feature
Command "feature" from hoblin/claude-ruby-marketplace, covering input format, context, workflow, step 1: setup and step 2: gather historical context.
speckit.specify
Create or update the feature specification from a natural language feature description.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.