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 skills add LeoLin990405/r-analytics-skill --skill rcmdcheckgit clone --depth 1 https://github.com/LeoLin990405/r-analytics-skillWrote 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/skills/leolin990405/r-analytics-skill/rcmdcheck)<a href="https://agentmods.dev/skills/leolin990405/r-analytics-skill/rcmdcheck"><img src="https://agentmods.dev/badge/skills/leolin990405/r-analytics-skill/rcmdcheck/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/skills/leolin990405/r-analytics-skill/rcmdcheck"><img src="https://agentmods.dev/badge/skills/leolin990405/r-analytics-skill/rcmdcheck.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.00024 | $0.00454 |
| Opus 5 | $0.00012 | $0.00227 |
| Sonnet 5 | $0.00005 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
rcmdcheck 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 8d 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
rcmdcheck
Run R CMD check from R.
Basic Usage
library(rcmdcheck)
# Check current package
rcmdcheck()
# Check specific package
rcmdcheck("path/to/package")
Options
# With arguments
rcmdcheck(args = c("--no-manual", "--as-cran"))
# Build arguments
rcmdcheck(build_args = "--no-build-vignettes")
# Check directory
rcmdcheck(check_dir = "check_output")
Common Arguments
# CRAN-like check
rcmdcheck(args = "--as-cran")
# Skip manual
rcmdcheck(args = "--no-manual")
# Skip vignettes
rcmdcheck(args = "--no-vignettes")
# Skip tests
rcmdcheck(args = "--no-tests")
# Skip examples
rcmdcheck(args = "--no-examples")
# Multiple
rcmdcheck(args = c("--no-manual", "--no-vignettes"))
Results
# Run check
res <- rcmdcheck()
# Access results
res$errors
res$warnings
res$notes
# Status
res$status # 0 = success
# Print summary
print(res)
Error on Issues
# Error if check fails
rcmdcheck(error_on = "error")
# Error on warnings too
rcmdcheck(error_on = "warning")
# Error on notes
rcmdcheck(error_on = "note")
CI Usage
# In CI scripts
rcmdcheck::rcmdcheck(
args = "--no-manual",
error_on = "warning",
check_dir = "check"
)
Compare Checks
# Compare two check results
compare_checks(check1, check2)
# Compare to CRAN
cran_check_results("packagename")
Revdep Checks
# Reverse dependency checks
library(revdepcheck)
revdep_check()
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.
- 8d ago First seen · 116 lines · 24 tokens per session scan A 109f480a388f
rcmdcheck is a skill published in the GitHub repository LeoLin990405/r-analytics-skill (5 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 454 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-09-03.
Other skills, from other repositories
change-request-to-go-live-protocol
Use this skill when a Dynamics 365 change request must be structured and progressed through impact assessment, fit-gap analysis, UAT sign-off, go/no-go decision, go-live execution, and hypercare using the Success by Design framework. Defines the full change-to-go-live flow — change request intake, solution blueprint…
environment-to-production-release-protocol
Use this skill when a Power Platform or Dynamics 365 solution must progress through a structured dev-to-test-to-production release pipeline using managed solutions and Power Platform pipelines, when rollback readiness must be verified before go-live, or when a deployment approval gate must be enforced. Defines the…
erp-crm-cutover-protocol
Use this skill when a Dynamics 365 ERP or CRM implementation is approaching go-live and must progress through mock migration, data reconciliation, cutover runbook execution, rollback testing, and the Success by Design go-live gate before production switchover. Orchestrates d365-data-migration-cutover-agent as primary…
argo-rollouts-progressive-delivery-review
Use this skill when reviewing Argo Rollouts progressive delivery configuration. Trigger when the user asks about canary or blue-green Rollout strategy correctness, AnalysisTemplate success/failure conditions, traffic weighting provider alignment, canaryService isolation, PDB deadlock risk with Rollout maxSurge…
betterthink
Enforce a stricter execution workflow for coding tasks: reduce ambiguity before editing, complete and verify one work item before starting the next, keep the project's instructions file lean and current when conventions or commands change, and screenshot-check UI work across mobile, tablet, and desktop. Use when the…
betterthink
Enforce a stricter execution workflow for coding tasks: reduce ambiguity before editing, complete and verify one work item before starting the next, keep the project's rules file lean and current when conventions or commands change, and screenshot-check UI work across mobile, tablet, and desktop. Use when the user…