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/doc-check)<a href="https://agentmods.dev/commands/data-wise/claude-plugins/doc-check"><img src="https://agentmods.dev/badge/commands/data-wise/claude-plugins/doc-check/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/doc-check"><img src="https://agentmods.dev/badge/commands/data-wise/claude-plugins/doc-check.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.00015 | $0.00516 |
| Opus 5.5 | $0.00006 | $0.00206 |
| Sonnet 5.5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
rforge:doc-check 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.
What it actually says
/rforge:doc-check - Documentation Drift Checker
Check for documentation inconsistencies and drift across your R package ecosystem.
What It Does
Uses the rforge_doc_check MCP tool to:
- Verify NEWS.md completeness
- Check API contract consistency
- Find outdated examples
- Identify missing documentation
- Cross-reference vignettes
Usage
# Check all documentation
/rforge:doc-check
# Check specific package
/rforge:doc-check medfit
# Detailed check with examples
/rforge:doc-check --detailed
Output
Returns documentation audit with:
- NEWS.md Status: Up-to-date or needs entries
- API Contracts: Consistency across packages
- Examples: Outdated or broken examples
- Vignettes: Cross-references and accuracy
- Recommendations: What to update
Examples
Clean Documentation
📝 DOCUMENTATION CHECK
NEWS.md: ✅ Current (last entry: 2025-01-15)
API Contracts: ✅ Consistent across ecosystem
Examples: ✅ All working
Vignettes: ✅ Up-to-date
Status: EXCELLENT
No action needed.
Documentation Drift
⚠️ DOCUMENTATION CHECK
NEWS.md: ⚠️ Missing 3 recent changes
• extract_mediation refactor (2025-01-10)
• New bootstrap method (2025-01-08)
• Bug fix #234 (2025-01-05)
API Contracts: ❌ Inconsistency detected
• probmed expects old signature
• medsim docs reference deprecated function
Examples: ⚠️ 2 outdated
• README example uses old API
• Vignette 2 has broken code
Recommendations:
1. Update NEWS.md (5 min)
2. Fix probmed function calls (15 min)
3. Update examples (20 min)
4. Regenerate vignettes (10 min)
Total work: ~50 minutes
Use When
- Before releases
- After API changes
- During code reviews
- Maintaining ecosystem health
Related Commands
/rforge:status- Overall health check/rforge:impact- See change impact/rforge:cascade- Plan documentation updates
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 · 94 lines · 15 tokens per session scan A 3d27be8d0c2a
rforge:doc-check is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 516 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
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.