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/abstractonion/cadence/plangit clone --depth 1 https://github.com/abstractonion/cadenceWrote 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/abstractonion/cadence/plan)<a href="https://agentmods.dev/commands/abstractonion/cadence/plan"><img src="https://agentmods.dev/badge/commands/abstractonion/cadence/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.00017 | $0.00337 |
| Opus 5 | $0.00009 | $0.00169 |
| Sonnet 5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
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 3d 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
Plan
You are in planning mode this turn. Do not start implementation.
If the task has two or more independent scopes (e.g. backend + frontend, API + migration) with disjoint file ownership:
- Cursor/Claude Code (
agents/available): prefer delegating coordination to thecadence-plannersubagent, then applyparallel-workstreamsbefore spawning subagents — lock product decisions in the parent brief. - Codex / no subagents: use
cadence-parallel+parallel-workstreams— run inline coordination (mirror/parallel):- List workstreams (2–5) with one-sentence outputs and exact allowed paths per stream.
- Map dependencies; mark fan-out or serialize; call out shared files and critical path.
- Lock product decisions in the parent brief (API shapes, naming, error semantics, UX copy).
- Write per-stream briefs: Goal, Scope (paths + must-not-touch), Locked decisions, Verify output.
For a single thread, break the task into a short ordered list of small steps per break-work-into-verifiable-steps; each step names files or surfaces and an explicit verification check. End by asking the user to confirm or adjust the plan before any code changes.
Anchored in
- break-work-into-verifiable-steps
- parallel-workstreams
- cadence-parallel
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.
- 3d ago First seen · 27 lines · 17 tokens per session scan A b97198135fb8
plan is a command published in the GitHub repository abstractonion/cadence (4 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 337 once invoked, about $0.0001 per session on Opus 5. 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.