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/status)<a href="https://agentmods.dev/commands/data-wise/claude-plugins/status"><img src="https://agentmods.dev/badge/commands/data-wise/claude-plugins/status/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/status"><img src="https://agentmods.dev/badge/commands/data-wise/claude-plugins/status.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.00016 | $0.04144 |
| Opus 5.5 | $0.00006 | $0.01658 |
| Sonnet 5.5 | $0.00003 | $0.00829 |
| Haiku 4.5 | $0.00002 | $0.00414 |
Grade A, and why
rforge:status 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 — 572 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rforge:status - Mode-Aware Status Dashboard
Get comprehensive status information for your R package ecosystem with explicit control over detail level.
Mode System
Current Mode: {{mode | default: "default"}}
Mode Selection
Parse the user's request to detect mode:
- If user explicitly provides "debug", "optimize", or "release" → use that mode
- Otherwise → use "default" mode (quick dashboard)
Default Mode (2-5 seconds)
Purpose: Daily check-ins, morning stand-up, quick validation
Behavior:
- Overall health score (0-100)
- Active warnings (critical severity only)
- Git status (clean/dirty, branch)
- Last update timestamp
- Quick summary of ecosystem state
Data Retrieved:
- Package count and names
- Critical issues only
- Basic test status (pass/fail)
- CRAN check status (if recent)
Time Budget: MUST complete in < 5 seconds
Output Format:
📊 STATUS: mediationverse ecosystem
Overall Health: 87/100 (B+)
✅ medfit 92/100
⚠️ probmed 78/100 (2 warnings)
✅ medsim 85/100
✅ mediationverse 91/100
Critical Issues: 1
• probmed: Missing NEWS.md entry
Last Updated: 2 hours ago
Git: Clean, branch: main
Debug Mode (15-30 seconds)
Purpose: Investigating issues, understanding problems, detailed diagnostics
Behavior:
- Per-package health breakdown
- All warnings (all severity levels)
- Dependency tree visualization
- Test coverage metrics per package
- Documentation coverage per package
- Known issues list with details
Data Retrieved:
- Complete dependency graph
- All test results with details
- Documentation completeness per function
- Recent changes analysis
- Build logs (if available)
- Environment diagnostics
Time Budget: SHOULD complete in < 30 seconds
Output Format:
📊 DETAILED STATUS: mediationverse ecosystem
Overall Health: 87/100 (B+)
═══════════════════════════════════════════
Package: medfit v2.1.0
═══════════════════════════════════════════
Health: 92/100 (A-)
Tests: 187/187 passing (94% coverage)
• R/mediation.R: 98% coverage
• R/bootstrap.R: 91% coverage
• R/utils.R: 87% coverage
CRAN: ✅ All checks OK
Docs: 24/25 functions documented (96%)
• Missing: .internal_helper
Dependencies: 12 direct, 34 total
✅ All current versions
Issues: 1 warning
⚠️ NEWS.md needs entry for v2.1.1
Last Updated: 2 hours ago
═══════════════════════════════════════════
Package: probmed v1.3.0
═══════════════════════════════════════════
Health: 78/100 (C+)
Tests: 95/98 passing (84% coverage)
❌ 3 failures in test-edge-cases.R
• Low coverage: R/sensitivity.R (67%)
CRAN: ⚠️ 2 NOTEs
• NOTE: Package size (3.2 MB)
• NOTE: GNU make required
Docs: 18/20 functions documented (90%)
• Missing: calc_internal, validate_args
Dependencies: 8 direct, 28 total
⚠️ 1 outdated: boot (1.3-28 → 1.3-30)
Issues: 4 warnings
⚠️ NEWS.md missing entry
⚠️ 3 test failures
⚠️ Low coverage on sensitivity.R
⚠️ Outdated dependency: boot
Last Updated: 5 hours ago
Dependency Tree:
medfit ← probmed ← medsim ← mediationverse
└─> boot, MASS, stats
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 · 572 lines · 16 tokens per session scan A ac13df8efde4
rforge:status is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 4,144 once invoked, about $0.0001 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
health
Run health checks on the Claude orchestration system.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.