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-promoteWrote 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-promote)<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/plan-promote"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/plan-promote.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.00344 |
| Opus 5 | $0.00000 | $0.00172 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
plan-promote 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-promote <note>
Bubble a T4 discovery up to T2 or T1. Alias for /aura-frog:plan promote "<note>" (v3.7.2+).
Usage
/aura-frog:plan-promote "Existing module X already provides Y — scope shrinks"
/aura-frog:plan-promote --to FEAT-007 "Auth needs Redis, not in scope"
/aura-frog:plan-promote --to INIT-001 "Need new initiative for migration"
Delegation
bash aura-frog/scripts/plans/promote-node.sh "<note>" [--to <ID>] [--source <ID>]
The script:
- Resolves source (default:
active.task) and target (default: source's grandparent — T4 → T2). - Appends
<source>@<ts>: <note>to the target's## Discoveriessection (creates if absent). - Bumps target's
revision. - Appends
history.jsonl event=promote.
What's promotable (architectural / design / scope-altering — NOT implementation details, test failures, file edits). Promotion does NOT auto-replan — it flags for review. Use /aura-frog:plan replan to act on the discovery.
Full protocol in commands/plan.md. Cannot promote from discarded|archived nodes.
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 · 32 lines · 0 tokens per session scan A 64ddf32bd7d0
plan-promote is a command published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 344 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
end-work
Complete work session with final checklist.
sync-linear
Sync current work with Linear ticket status.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
go
You are the Project Kickstart agent. Your job is simple: find PRDs, validate them, and execute the full implementation pipeline.
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.