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-nextWrote 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-next)<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/plan-next"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/plan-next/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.
<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/plan-next"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/plan-next.svg" alt="Reviewed on agentmods" width="80" 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.00302 |
| Opus 5.5 | $0.00000 | $0.00121 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
plan-next 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 1mo 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-next
Return and activate the next ready T4 task. Alias for /aura-frog:plan next (v3.7.2+).
Usage
/aura-frog:plan-next
Delegation
bash aura-frog/scripts/plans/next-task.sh [--plans-dir <path>] [--dry-run]
The script collects T4 children of the active T3 with status: planned AND all depends_on in {done, active} — from graph-index.json when the project has one and it is fresh, otherwise by rescanning the task files (always correct, just slower; next-task.sh --rebuild regenerates the index). It picks the first, mutates it to status: active under the dispatch lock, sets active.task, and appends history.jsonl {"verb":"next"}.
Then surface to the user: Next ready: <TASK-ID> (<intent>). To execute: /aura-frog:run <one-line description> — auto-anchors via the Run ↔ Plan bridge.
Full protocol in commands/plan.md. Frozen tasks are excluded — thaw via /aura-frog:plan thaw first.
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.
- 1mo ago First seen · 26 lines · 0 tokens per session scan A dd415f01f2a4
plan-next is a command published in the GitHub repository nguyenthienthanh/aura-frog (25 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 302 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
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
sync-linear
Sync current work with Linear ticket status.
end-work
Complete work session with final checklist.
go
You are the Project Kickstart agent. Your job is simple: find PRDs, validate them, and execute the full implementation pipeline.
blueprint
A command for discussing and maintaining confirmed product requirements in one shared product blueprint.
feature
Role: Per-feature quality pipeline that takes a story or feature description from zero to a committed, documented, tested, and evaluated implementation. No stage is skipped. No commit happens without the evaluator's approval.