Borrowing it
Nothing to install: this file belongs to r3bl-org/r3bl-open-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/r3bl-org/r3bl-open-core/main/.agents/skills/run-clippy/SKILL.mdgit clone --depth 1 https://github.com/r3bl-org/r3bl-open-coreWrote 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/r3bl-org/r3bl-open-core/run-clippy)<a href="https://agentmods.dev/skills/r3bl-org/r3bl-open-core/run-clippy"><img src="https://agentmods.dev/badge/skills/r3bl-org/r3bl-open-core/run-clippy/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/r3bl-org/r3bl-open-core/run-clippy"><img src="https://agentmods.dev/badge/skills/r3bl-org/r3bl-open-core/run-clippy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.01696 |
| Opus 5 | $0.00018 | $0.00848 |
| Sonnet 5 | $0.00007 | $0.00339 |
| Haiku 4.5 | $0.00004 | $0.00170 |
Grade A, and why
run-clippy 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 10d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clippy Fixes and Code Style Enforcement
When to Use
- After making code changes
- Fixing clippy warnings
- Ensuring comment punctuation consistency
- Enforcing module organization patterns
- Before creating commits
- When user says "run clippy", "fix style", "format code", "check lints", etc.
Instructions
Run these steps in order to enforce code quality and style standards:
Step 1: Run Clippy
Run clippy to catch linting issues:
./check.fish --clippy
# (runs: cargo clippy --all-targets)
Review and fix all warnings. For auto-fixable issues:
cargo clippy --all-targets --fix --allow-dirty
Common clippy categories:
- Correctness: Potential bugs and logic errors (must fix)
- Performance: Inefficient code patterns (should fix)
- Style: Idiomatic Rust patterns (should fix)
- Pedantic: Opinionated style (optional, review case-by-case)
- Complexity: Overly complex code (refactor if excessive)
Step 2: Enforce Comment Punctuation
Apply these punctuation rules to all comments (not rustdoc /// or //!, but regular // comments) in the git working tree:
Rule 1: Single-line Standalone Comments
Add a period at the end:
// This is a single line comment.
Rule 2: Multi-line Wrapped Comments (One Logical Sentence)
Period ONLY on the last line:
// This is a long line that wraps
// to the next line.
Rule 3: Multiple Independent Single-line Comments
Each gets its own period:
// First independent thought.
// Second independent thought.
How to Identify Wrapped vs Independent
Wrapped comments:
- The second line continues the grammatical structure of the first
- Reads as one sentence if combined
Independent comments:
- Each line could stand alone as a complete thought
- Separate sentences with distinct subjects
Step 3: Enforce Clean Imports (No Inline Absolute Paths)
Scan the changed files for any inline absolute paths (e.g., crate::Type, crate::function!) and replace them with proper use statements at the top of the file.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 215 lines · 36 tokens per session scan A e79ad86a92ad
run-clippy is a skill published in the GitHub repository r3bl-org/r3bl-open-core (483 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 1,696 once invoked, about $0.0002 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 skills, from other repositories
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
cw-slice
Use before writing code for any Codewhale feature, upgrade, or refactor: find the existing owner of the behavior, bound the change to one reviewable slice, and fix the evidence bar before you start.
cw-dogfood
Use when a Codewhale change needs proving in the real product, or when asked to build/install/dogfood the local binaries: stamped release build, atomic install, fresh-shell verification, and the manual QA that gates cannot cover.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
cw-handoff
Use when writing a Codewhale takeover prompt, continuation note, or end-of-session summary for another agent or a later session: a paste-ready handoff grounded in live state, with done/suspected/blocked kept separate.
cw-orient
Use at the start of any Codewhale work session, or when unsure which checkout, branch, or worktree is authoritative: establish live repo truth before reading a plan or editing a file.