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/check-code-quality/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/check-code-quality)<a href="https://agentmods.dev/skills/r3bl-org/r3bl-open-core/check-code-quality"><img src="https://agentmods.dev/badge/skills/r3bl-org/r3bl-open-core/check-code-quality.svg" alt="Measured on agentmods" 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.00031 | $0.03565 |
| Opus 5 | $0.00015 | $0.01783 |
| Sonnet 5 | $0.00006 | $0.00713 |
| Haiku 4.5 | $0.00003 | $0.00357 |
Grade A, and why
check-code-quality 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 yesterday.
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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Code Quality Checks
When to Use
- After completing significant code changes
- Before creating commits
- Before creating pull requests
- When user says "check code quality", "run quality checks", "make sure code is good", etc.
Non-Blocking Execution via Subagents
Long-running verification commands (such as ./check.fish --test, ./check.fish --doc, ./check.fish --quick-doc, and ./check.fish --full) can take multiple minutes. To keep the primary conversation responsive and unblocked:
- Fast Synchronous Checks: Lightweight checks like
./check.fish --check(fast typecheck) and./check.fish --fmttake only a few seconds and can run directly in the conversation. - Long-Running Checks via Subagent: Delegate time-consuming checks to a background subagent (e.g.,
invoke_subagentwithTypeName: "self"). - Continuous Collaboration: While the subagent runs tests or builds docs in the background, the primary agent remains completely free to converse, review diffs, answer questions, or plan next steps with the user.
Quick Approach (Recommended)
Run the comprehensive check script which handles everything automatically:
./check.fish --full
This runs all checks in order: typecheck → build → clippy → tests → doctests → docs
Benefits of using check.fish --full:
- ICE recovery: Automatically cleans cache and retries on Internal Compiler Errors
- Toolchain escalation: If ICE persists, escalates to
rust-toolchain-update.fishto find a stable nightly - Config change detection: Auto-cleans stale artifacts when Cargo.toml or toolchain changes
- Performance optimized: Uses tmpfs, ionice, and parallel jobs for speed
Other check.fish Commands
For granular control, use individual commands:
| Command | What it runs |
|---|---|
./check.fish --check |
cargo check (fast typecheck) |
./check.fish --build |
cargo build (compile production) |
./check.fish --clippy |
cargo clippy --all-targets (linting) |
./check.fish --fmt |
cargo fmt + cargo rustdoc-fmt on git-changed files |
./check.fish --test |
cargo test + doctests |
./check.fish --doc |
cargo doc --no-deps (quick docs) |
./check.fish --quick-doc |
cargo doc --no-deps (fastest, no staging/sync) |
./check.fish --full |
All of the above + lychee link rot check |
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.
- yesterday Changed · +15 lines 459e76a26bfd
- 7d ago First seen · 292 lines · 31 tokens per session scan A 0812b12cd480
check-code-quality is a skill published in the GitHub repository r3bl-org/r3bl-open-core (483 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 3,565 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-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-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.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-compile-issues
Triage N GitHub issues into a coverage matrix: fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
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.