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.
npx agentmods add commands/nguyenthienthanh/aura-frog/plangit clone --depth 1 https://github.com/nguyenthienthanh/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)<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/plan"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/plan.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 | $0.00000 | $0.02041 |
| Opus 5 | $0.00000 | $0.01020 |
| Sonnet 5 | $0.00000 | $0.00408 |
| Haiku 4.5 | $0.00000 | $0.00204 |
Grade A, and why
plan 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aura-frog:plan
Hierarchical planning entry point — all 11 plan verbs in one command.
v3.7.2 consolidates /aura-frog:plan-* (10 commands) into a single dispatcher that routes via the plan-orchestrator skill. The legacy plan-<verb> aliases still work as thin stubs.
Category: Planning
Scope: Project-local (writes to .claude/plans/)
Two invocation modes
1. Bootstrap (no args)
/aura-frog:plan
Initialises .claude/plans/ and interview-bootstraps T0 (Mission) → T1 (Initiative) → T2 (Feature).
2. Verb dispatch
/aura-frog:plan <verb> [target] [flags]
The 11 verbs and their backing scripts (see skills/plan-orchestrator/SKILL.md for the full verb table):
| Verb | Backing script | Purpose |
|---|---|---|
bootstrap (default) |
new-plan.sh |
Initial T0/T1/T2 — same as no-arg form |
expand <id> |
expand-node.sh |
Decompose one tier down (T1→T2 / T2→T3 / T3→T4) |
next |
next-task.sh |
Dispatch next ready T4 (scans active story's task files) |
status |
render-plan-tree.sh |
Render the tree as ASCII |
replan <id> |
replan-node.sh |
Force replan + discard descendants |
promote "<note>" |
promote-node.sh |
Bubble T4 discovery up to T2/T1 |
archive <id> |
archive-feature.sh |
Compress completed T2+ to summary |
undo [<id>] |
undo-decision.sh |
Restore latest checkpoint (LIFO) |
freeze <id> |
freeze-branch.sh |
Cascade-freeze descendants |
thaw <id> |
thaw-branch.sh |
Reverse freeze |
conflicts <sub> |
conflicts-scan.sh |
List/show/resolve/history/check |
Each verb takes its own flags — see aura-frog/commands/plan-<verb>.md for full per-verb docs (alias stubs).
Power-user shortcuts
/aura-frog:plan next # bare verb, no target
/aura-frog:plan expand FEAT-A # explicit ID
/aura-frog:plan expand auth # title substring → resolve-node.sh
/aura-frog:plan freeze --active "blocked on db" # current active.task
/aura-frog:plan undo # last mutation, any node
/aura-frog:plan conflicts list --open # subcommand chaining
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.
- 4d ago First seen · 177 lines · 0 tokens per session scan A 6ff15f60b926
plan is a command published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,041 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.
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.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit.clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.