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/ab604/claude-code-r-skills/verifygit clone --depth 1 https://github.com/ab604/claude-code-r-skillsWrote 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/ab604/claude-code-r-skills/verify)<a href="https://agentmods.dev/commands/ab604/claude-code-r-skills/verify"><img src="https://agentmods.dev/badge/commands/ab604/claude-code-r-skills/verify.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.00637 |
| Opus 5 | $0.00012 | $0.00318 |
| Sonnet 5 | $0.00005 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
verify 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 4d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/verify - R Verification Loop
Run all quality gates before committing code. Produces a READY or NOT READY verdict.
When to Use
- Before every commit
- After implementing a feature or fix
- Before opening a pull request
- Any time you want a full quality check
Verification Phases
Run each phase in order. A failure in any phase blocks the verdict.
Phase 1: Build Check
devtools::check(quiet = TRUE)
Pass criteria: 0 errors, 0 warnings, 0 notes (or only expected notes).
Phase 2: Style Check
styler::style_pkg()
Auto-fixes style. Re-check for any manual fixes needed.
Phase 3: Lint Check
lintr::lint_package()
Pass criteria: 0 lints. Fix all flagged issues before proceeding.
Phase 4: Test Coverage
covr::package_coverage()
Pass criteria: ≥80% overall coverage. Critical paths (validation, stats) require 100%.
Phase 5: Code Review
Invoke the code-reviewer agent to check uncommitted changes:
/code-review
Pass criteria: No CRITICAL or HIGH issues.
Phase 6: Diff Review
git diff --stat HEAD
git diff HEAD
Manually confirm:
- No unintended files changed
- No debug code or
print()/cat()left in - No hardcoded paths or credentials
- Commit message ready
Verdict Format
## Verification Report
| Phase | Status | Notes |
|----------------|--------|--------------------------------|
| Build check | ✅ PASS | 0 errors, 0 warnings |
| Style check | ✅ PASS | Auto-fixed 3 files |
| Lint check | ✅ PASS | 0 lints |
| Test coverage | ✅ PASS | 87% overall |
| Code review | ✅ PASS | No CRITICAL/HIGH issues |
| Diff review | ✅ PASS | Changes look correct |
## Verdict: ✅ READY TO COMMIT
Next step: commit with a descriptive message.
Or if issues found:
## Verdict: ❌ NOT READY
**Blocking issues:**
1. [Phase] - [specific issue]
2. [Phase] - [specific issue]
Fix all blocking issues and re-run /verify.
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.
- 4d ago First seen · 121 lines · 24 tokens per session scan A ff567c0e84c0
verify is a command published in the GitHub repository ab604/claude-code-r-skills (197 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 637 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.