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.
git clone --depth 1 https://github.com/Data-Wise/claude-pluginsWrote 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/data-wise/claude-plugins/cascade)<a href="https://agentmods.dev/commands/data-wise/claude-plugins/cascade"><img src="https://agentmods.dev/badge/commands/data-wise/claude-plugins/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/commands/data-wise/claude-plugins/cascade"><img src="https://agentmods.dev/badge/commands/data-wise/claude-plugins/cascade.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00657 |
| Opus 5.5 | $0.00004 | $0.00263 |
| Sonnet 5.5 | $0.00002 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
rforge: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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rforge:cascade - Cascade Update Planner
Plan coordinated updates across your R package ecosystem dependencies.
What It Does
Uses the rforge_cascade_plan MCP tool to:
- Create update sequence
- Identify blocking issues
- Estimate timeline
- Generate task checklist
- Coordinate CRAN submissions
Usage
# Plan cascade for current changes
/rforge:cascade
# Plan for version bump
/rforge:cascade "medfit 2.2.0"
# Detailed cascade plan
/rforge:cascade --detailed
Output
Returns cascade plan with:
- Update Sequence: Topological order
- Per-Package Tasks: What needs updating
- Timeline: Estimated completion
- Blockers: Issues to resolve first
- CRAN Strategy: Submission sequence
Examples
Simple Cascade
🔄 CASCADE PLAN: medfit 2.1.0 → 2.2.0
Phase 1: Core (Week 1)
1. medfit
✓ Update version
✓ Run tests
✓ Update NEWS.md
⏱ 2 hours
Phase 2: Implementations (Week 2)
2. probmed
• Update medfit dependency
• Re-run tests
⏱ 1 hour
3. medsim
• Update medfit dependency
• Update vignette
⏱ 2 hours
Phase 3: Meta (Week 2)
4. mediationverse
• Update all dependencies
⏱ 30 min
Total time: 5.5 hours over 2 weeks
Breaking Change Cascade
⚠️ CASCADE PLAN: Breaking API change
Phase 1: Preparation (Week 1)
1. Add deprecation warnings
2. Update all docs
3. Create migration guide
⏱ 4 hours
Phase 2: Core Package (Week 2)
1. medfit → 3.0.0 (major bump)
• Implement breaking changes
• Update all tests
⏱ 8 hours
Phase 3: Dependent Updates (Weeks 3-4)
2-4. Update all dependents
Each: API migration + tests
⏱ 12 hours total
Phase 4: Meta Package (Week 5)
5. mediationverse version alignment
⏱ 1 hour
Total: ~25 hours over 5 weeks
Blockers: Need CRAN approval for medfit first
Use When
- Planning major updates
- Coordinating releases
- Managing breaking changes
- Scheduling CRAN submissions
Related Commands
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.
- 1mo ago First seen · 115 lines · 11 tokens per session scan A 44f2c9c85644
rforge:cascade is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 657 once invoked, about $0.0000 per session on Opus 5.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
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.