Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nguyenthienthanh/aura-frognpx agentmods add commands/nguyenthienthanh/aura-frog/plan-replanWrote 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-replan)<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/plan-replan"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/plan-replan.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-replan 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 7d 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-replan <id>
Force replan of a node and all descendants. Alias for /aura-frog:plan replan <id> (v3.7.2+).
Usage
/aura-frog:plan-replan TASK-00101
/aura-frog:plan-replan STORY-0042 --reason "design pivot"
/aura-frog:plan-replan FEAT-A --avoid src/legacy
Delegation
bash aura-frog/scripts/plans/replan-node.sh <ID> [--reason "..."] [--avoid <path-or-id>] [--force]
The script:
- Refuses on
replan_count >= replan_budgetunless--force. - Saves a per-node checkpoint.
- Marks all descendants
status: discarded(preserves IDs). - Bumps target's
revision+replan_count, recordslast_replan_at/last_replan_reason. - Appends
history.jsonl event=replan.
The caller (or replanner agent in Milestone B+) is then responsible for proposing the new subtree shape.
Full protocol in commands/plan.md. Cannot replan done|archived — use /aura-frog:plan undo first if you need to revert.
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.
- 7d ago First seen · 33 lines · 0 tokens per session scan A 6281f2ed76e3
plan-replan is a command published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 2d ago), 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
create_plan
Create detailed implementation plans through interactive research and iteration.
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.
research_codebase
Document codebase as-is with thoughts directory for historical context.
resume_handoff
Resume work from handoff document with context analysis and validation.
create_handoff
Create handoff document for transferring work to another session.
feature
Command "feature" from hoblin/claude-ruby-marketplace, covering input format, context, workflow, step 1: setup and step 2: gather historical context.