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/taoidle/plan-cascade/spec-resumegit clone --depth 1 https://github.com/Taoidle/plan-cascadeWrote 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/taoidle/plan-cascade/spec-resume)<a href="https://agentmods.dev/commands/taoidle/plan-cascade/spec-resume"><img src="https://agentmods.dev/badge/commands/taoidle/plan-cascade/spec-resume.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.00039 | $0.00113 |
| Opus 5 | $0.00019 | $0.00056 |
| Sonnet 5 | $0.00008 | $0.00023 |
| Haiku 4.5 | $0.00004 | $0.00011 |
Grade A, and why
spec-resume 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
Plan Cascade - Spec Resume
Resume an in-progress spec interview in the current directory (or --output-dir).
Step 1: Run Resume (CLI)
uv run --project "${CLAUDE_PLUGIN_ROOT}" plan-cascade spec resume --output-dir "<output-dir>" --flow <flow>
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 · 15 lines · 39 tokens per session scan A 925b5831376b
spec-resume is a command published in the GitHub repository Taoidle/plan-cascade (131 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 113 once invoked, about $0.0002 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-30.
Other commands, from other repositories
setup-video-vision
Interactive setup wizard for claude-video-vision — configure backend, whisper, frames, and verify dependencies.
create-epo-patent
Create a complete EPO-compliant patent application from invention disclosure through filing-ready package.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.
search-flights
Search award flight availability across airlines.
chronicle
One-time codebase onboarding — interactively extracts your team's conventions, identifies reference files, and generates CLAUDE.md sections so Claude codes the way your team does. Run once per project.
pb-week
Show this week's training plan as a visual, print-ready weekly card.