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/quickgit 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.00017 | $0.00829 |
| Opus 5 | $0.00009 | $0.00415 |
| Sonnet 5 | $0.00003 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
rforge:quick 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rforge:quick - Ultra-Fast R Package Analysis
Lightning-fast analysis using only quick MCP tools. Results in < 10 seconds guaranteed.
Usage
# Ultra-fast analysis
/rforge:quick
# With context
/rforge:quick "Update bootstrap code"
# Specific package
/rforge:quick --package /path/to/RMediation
What It Does
Runs 4 fast MCP tools in parallel:
- Quick Impact - Dependency check (5-8 sec)
- Quick Tests - Test status (3-5 sec)
- Quick Docs - Documentation check (2-3 sec)
- Quick Health - Overall score (5-7 sec)
Total time: ~10 seconds (parallel execution)
Output Example
⚡ Quick analysis running...
[████████░░] Impact 80%
[██████████] Tests 100% ✓
[██████████] Docs 100% ✓
[████░░░░░░] Health 40%
✅ Done! (8.2 seconds)
📊 QUICK SUMMARY:
✅ Impact: 2 packages (MEDIUM)
✅ Tests: 187/187 passing
⚠️ Docs: NEWS.md needs update
✅ Health: 87/100 (B+)
Next: Run /rforge:analyze for detailed recommendations
When to Use
Use /rforge:quick when:
- ✅ You want instant feedback
- ✅ You're just checking status
- ✅ You don't need deep analysis
- ✅ You're in a hurry
- ✅ You're doing quick iterations
Don't use when:
- ❌ Preparing for CRAN release (use
/rforge:thorough) - ❌ Need detailed cascade plan (use
/rforge:analyze) - ❌ Want comprehensive coverage report (use
/rforge:thorough)
Tools Used
| Tool | What It Checks | Time |
|---|---|---|
rforge_quick_impact |
Dependency graph | 5-8s |
rforge_quick_tests |
Test files & last results | 3-5s |
rforge_quick_docs |
NEWS, vignettes, README | 2-3s |
rforge_quick_health |
Overall package health | 5-7s |
All run in parallel → total ~10 seconds
Options
--package <path>- Explicit package path--json- Raw JSON output--no-progress- Skip progress bars
Example Output
{
"mode": "quick",
"duration_seconds": 8.2,
"results": {
"impact": {
"affected_packages": 2,
"severity": "MEDIUM"
},
"tests": {
"passing": 187,
"total": 187,
"coverage": 94
},
"docs": {
"has_news": true,
"needs_update": true
},
"health": {
"score": 87,
"grade": "B+"
}
}
}
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 · 130 lines · 17 tokens per session scan A 62b429d678ec
rforge:quick is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 829 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.