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/plan-conflictsgit 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-conflicts)<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/plan-conflicts"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/plan-conflicts.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.00434 |
| Opus 5 | $0.00000 | $0.00217 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
plan-conflicts 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.
What it actually says
/aura-frog:plan-conflicts
Inspect, resolve, audit plan-tree conflicts. Alias for /aura-frog:plan conflicts <sub> (v3.7.2+).
Usage
/aura-frog:plan-conflicts list # all (open + resolved)
/aura-frog:plan-conflicts list --open
/aura-frog:plan-conflicts show <CONFLICT-ID>
/aura-frog:plan-conflicts resolve <CONFLICT-ID> <choice>
/aura-frog:plan-conflicts history
/aura-frog:plan-conflicts check # run L1+L2 detector against active.task
<choice>: accept-proposed | accept-blocker | sequential | freeze-both | escalate.
Delegation
bash aura-frog/scripts/plans/conflicts-scan.sh <list|show|resolve|history|check> [args...]
The script:
- list — folds
conflicts.jsonlperconflict_id(latest record wins), optionally filtered by--open(records with noresolution). - show — prints every record matching
conflict_id. - resolve — appends a new record with the user's choice + writes
history.jsonl event=conflicts.resolve. Validates choice against the allowed set. - history — dumps
conflicts.jsonlraw. - check — runs the
conflict-detectorskill for on-demand L1+L2 detection (Tier-1 per Tech Spec §21); thepre-dispatch-conflict-check.cjshook performs the same automatically before each dispatch.
Full per-choice mutation semantics (accept-proposed discards blocker, sequential sets depends_on, freeze-both cascades, etc.) are documented in commands/plan.md and the Tech Spec §21.5.
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.
- 4d ago First seen · 36 lines · 0 tokens per session scan A 77f82b11d695
plan-conflicts 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 434 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.