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/rpkg-checkgit 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.00000 | $0.00334 |
| Opus 5 | $0.00000 | $0.00167 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
rpkg-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 2d 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
R Package Quick Check
You are performing a quick health check on an R package.
Task
Check R package at: $ARGUMENTS
If no path specified, check current directory.
Quick Check Process
Step 1: Basic Info
Read DESCRIPTION file:
- Package name and version
- Dependencies (Imports, Suggests)
- R version requirement
Step 2: R CMD Check
Run r_check tool with default settings.
Step 3: Test Summary
Run r_test tool to get test results.
Step 4: Documentation Check
- Are all exported functions documented?
- Do examples run without error?
- Is there a README?
Step 5: Code Quality
- Any obvious style issues?
- Are there TODOs or FIXMEs?
- Is test coverage adequate?
Output Format
## Package Check: [package-name] v[version]
### Status: 🟢 / 🟡 / 🔴
### R CMD Check
- Errors: X
- Warnings: Y
- Notes: Z
### Tests
- Passed: X
- Failed: Y
- Coverage: Z%
### Documentation
- [ ] All exports documented
- [ ] Examples run
- [ ] README exists
### Issues Found
1. [Issue 1]
2. [Issue 2]
### Recommended Actions
1. [Action 1]
2. [Action 2]
Tools to Use
- r_check
- r_test
- Read (for DESCRIPTION, README)
- Grep (for TODOs, FIXMEs)
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.
- 2d ago First seen · 71 lines · 0 tokens per session scan A ee2616eaa6cb
rpkg-check is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 334 tokens. 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.