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 skills add Parcha-ai/parcha-skills --skill cascadegit clone --depth 1 https://github.com/Parcha-ai/parcha-skillsWrote 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/skills/parcha-ai/parcha-skills/cascade)<a href="https://agentmods.dev/skills/parcha-ai/parcha-skills/cascade"><img src="https://agentmods.dev/badge/skills/parcha-ai/parcha-skills/cascade/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/skills/parcha-ai/parcha-skills/cascade"><img src="https://agentmods.dev/badge/skills/parcha-ai/parcha-skills/cascade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00417 |
| Opus 5 | $0.00018 | $0.00209 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
cascade 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
Cascade
Keep one living plan in .cascade/<project>.md or the existing project plan:
- Outcome and final acceptance check.
- Context needed to resume: workspace, constraints, decisions, source links.
- Tasks: ID, deliverable, dependencies, exit check, status, evidence.
- Current owners, blockers, and next actions.
Decompose. Split by verifiable outcomes or subsystems; detail only near-term work. Expand large tasks into children while retaining the parent's acceptance check. Convert chains into dependency graphs by keeping actual prerequisites and removing ordering that serves no dependency.
Execute. Pick tasks whose prerequisites passed. Build, verify, update the plan, repeat while
authorized work remains. Use todo, doing, done, blocked. Failed checks remain unfinished;
change approach when attempts stop producing information. Respect session limits and continue
independent work when a task is blocked.
Parallelize. Use available subagents for independent ready tasks. Give each worker context, owned files or worktree, deliverable, and exit check. Serialize overlapping edits. Workers return changes, evidence, and unresolved issues; the lead owns integration and the plan. Mirror the graph into native tasks when useful; otherwise the file suffices.
Verify. Mark done only when the exit check passes on the actual candidate. Record check, result, and revision or working-tree identity. Test relevant failure cases; establish a baseline for measured improvements. Never weaken acceptance to hide failure. Verify the assembled system against the original outcome after its required tasks pass.
Resume. Save progress at meaningful boundaries and before handoff. Compare the plan with actual files and workers; recheck stale evidence. Continue until the overall acceptance passes or no authorized work can advance. Leave concrete blockers and next actions when stopping.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -97 lines · -51 tokens per session 277fcbf73c90
- 10d ago First seen · 134 lines · 87 tokens per session scan A 3ef51c51a276
cascade is a skill published in the GitHub repository Parcha-ai/parcha-skills (59 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 417 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.