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/data-wise/claude-plugins/releasegit clone --depth 1 https://github.com/Data-Wise/claude-pluginsWhat 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.00013 | $0.00618 |
| Opus 5 | $0.00006 | $0.00309 |
| Sonnet 5 | $0.00003 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
rforge:release 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 yesterday.
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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rforge:release - CRAN Release Planner
Plan the optimal CRAN submission sequence for your R package ecosystem.
What It Does
Uses the rforge_release_plan MCP tool to:
- Calculate submission order
- Identify blockers
- Check readiness
- Estimate approval timeline
- Generate submission checklist
Usage
# Plan release for ecosystem
/rforge:release
# Plan for specific package
/rforge:release medfit
# Detailed release plan
/rforge:release --detailed
Output
Returns release plan with:
- Submission Order: Dependency-based sequence
- Readiness Check: Per-package status
- Blockers: What's preventing releases
- Timeline: Expected approval dates
- Checklist: Pre-submission tasks
Examples
Simple Release Plan
🚀 CRAN RELEASE PLAN
Submission Order (by dependency):
1. medfit v2.2.0
Status: ✅ Ready
Blockers: None
Submit: Now
2. probmed v1.5.0
Status: ⏳ Waiting (needs medfit on CRAN)
Blockers: medfit not yet approved
Submit: +2 weeks (after medfit approval)
3. medsim v1.3.0
Status: ⏳ Waiting
Submit: +2 weeks
4. mediationverse v1.1.0
Status: ⏳ Waiting (needs all deps)
Submit: +4 weeks
Timeline: 4-6 weeks total
Complex Release (With Blockers)
⚠️ CRAN RELEASE PLAN
Submission Order:
1. medfit v2.2.0
Status: ❌ NOT READY
Blockers:
• 3 failing tests
• NEWS.md incomplete
• R CMD check has 1 NOTE
Fix time: ~4 hours
2. probmed v1.5.0
Status: ✅ Ready (but blocked by medfit)
Blockers: Waiting for medfit
3-4. [Waiting for previous]
Recommendations:
1. Fix medfit blockers (4 hours)
2. Submit medfit
3. Wait for approval (~2 weeks)
4. Submit dependents in parallel
5. Wait for approvals (~2 weeks)
6. Submit meta-package
Total timeline: 5-7 weeks
Use When
- Planning major releases
- Coordinating ecosystem updates
- Before CRAN submissions
- Managing versioning strategy
Related Commands
/rforge:status- Check readiness/rforge:cascade- Plan updates/rforge:deps- See dependency order
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.
- yesterday First seen · 112 lines · 13 tokens per session scan A 28af30b65580
rforge:release is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 5d ago), licensed MIT. It adds 13 tokens to every session and 618 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.