Borrowing it
Nothing to install: this file belongs to arthjean/rust-doctor. 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/arthjean/rust-doctor/main/.claude/skills/rule-admit/SKILL.mdgit clone --depth 1 https://github.com/arthjean/rust-doctorWrote 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/arthjean/rust-doctor/rule-admit)<a href="https://agentmods.dev/skills/arthjean/rust-doctor/rule-admit"><img src="https://agentmods.dev/badge/skills/arthjean/rust-doctor/rule-admit/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/arthjean/rust-doctor/rule-admit"><img src="https://agentmods.dev/badge/skills/arthjean/rust-doctor/rule-admit.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.00098 | $0.02239 |
| Opus 5 | $0.00049 | $0.01120 |
| Sonnet 5 | $0.00020 | $0.00448 |
| Haiku 4.5 | $0.00010 | $0.00224 |
Grade A, and why
rule-admit 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 9d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Admit one rule
Admission is one rule at a time. The catalog is small enough that every counter around it is written out by hand, so the work is less about the rule than about leaving nothing out of sync. Everything below is enforced by a test: skipping a step fails the suite, it does not slip through.
Read the "Admitting a rule" section of docs/catalog-and-corpus.md and
"Invariants the tests enforce" in docs/testing.md first. Verify the suite is green before starting, so that a failure
during the run belongs to the rule.
Step 1: Record what the rule catches
Take the toolchain's own description:
clippy-driver -W help | grep <lint-name>
That line is the catches field, verbatim. It has to match, a test compares
them. A native detector has no upstream line, so write one sentence naming the
pattern, not the fix.
Pick the category and the tier, and check the pair against TIER_WINDOWS in
src/policy/catalog/validate.rs. Write help as an instruction to the user: what to do
instead, in one sentence, without restating the problem.
Step 2: Build the trigger fixture
The rule needs a place where a test sees it fire. Follow the pattern of the rules admitted before it rather than inventing one.
For a lint whose dimension matches an existing pack, add the triggering form to
tests/fixtures/score-credibility/packs/<pack>/src/lib.rs, the quiet
counterpart to src/negatives.rs of the same pack, and the expected diagnostic
to the pack's oracle.json under positive, with code, category, tier,
path, line and occurrences. The packs are panic, performance and
concurrency.
Otherwise use the isolated form: a crate under
tests/fixtures/rule-scaling-kernel/positive/<kebab-name>/ and an entry in
tests/fixtures/rule-scaling-kernel/oracle.json under rules, carrying id,
category, help, clippy_default, message, positive_fixture and its
spans.
The negative form matters as much as the positive one. A rule with no recorded silence is a rule nobody has checked for over-reach.
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.
- 9d ago First seen · 202 lines · 98 tokens per session scan A 995e9fdd83cf
rule-admit is a skill published in the GitHub repository arthjean/rust-doctor (18 stars, last pushed 2d ago), licensed Apache-2.0. It adds 98 tokens to every session and 2,239 once invoked, about $0.0005 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
rust-quality-gate
PM-invocable protocol for running and interpreting Rust quality gates in the trusty-tools monorepo: fmt, clippy, and test in strict sequence before any merge.
Complete Rust Development
A comprehensive skill for Rust development that combines error handling, testing, and logging patterns. Demonstrates the 'includes' composition feature by merging content from multiple standalone skills.
project-chmonitor-verify-skill
Project-local .cursor/skills/verify-chmonitor drives the Rust CLI; default doctor is identity-only.
rust-testing-quality
Use when writing, organizing, or running Rust tests — unit, integration, doc-tests, proptest, criterion benchmarks, or cargo-mutants. Not for CI pipeline wiring (rust-tooling-cicd).
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
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.