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.
git clone --depth 1 https://github.com/mathisk2095/jko-claude-pluginsWrote 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/mathisk2095/jko-claude-plugins/rust-polish)<a href="https://agentmods.dev/commands/mathisk2095/jko-claude-plugins/rust-polish"><img src="https://agentmods.dev/badge/commands/mathisk2095/jko-claude-plugins/rust-polish/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/commands/mathisk2095/jko-claude-plugins/rust-polish"><img src="https://agentmods.dev/badge/commands/mathisk2095/jko-claude-plugins/rust-polish.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.00041 | $0.00692 |
| Opus 5.5 | $0.00016 | $0.00277 |
| Sonnet 5.5 | $0.00008 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
rust-polish 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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Polish
The final pass before merge. Polish is the discipline of caring about what most people skip. Do not polish work that is not functionally complete.
The 10-Dimension Checklist
Work through each dimension in order.
1. Clippy Clean
cargo clippy --all-targets --all-features -- -D warnings 2>&1 | head -40
Fix every warning. No suppressions without #[expect(lint, reason = "...")].
2. Formatting
cargo fmt --check
If any diffs, run cargo fmt.
3. Dead Code
rg --type rust '(todo!|unimplemented!|#\[allow\(dead_code|#\[allow\(unused)' src/ -n
Remove all todo!(), unimplemented!(), #[allow(dead_code)], #[allow(unused)]. Either use it or delete it.
4. Debug Artifacts
rg --type rust '(println!|dbg!|eprintln!)' src/ --glob '!*test*' -n
Remove or replace with structured logging (tracing/log).
5. Documentation
cargo doc --no-deps 2>&1 | rg 'warning' | head -20
Every pub item needs a doc comment. First line: complete sentence, third person, ends with period. Add # Examples for key types and functions.
6. Error Handling Completeness
Scan for:
let _ = fallible_call()— is the error intentionally discarded? Add a comment if so.- Bare
?without.context()— add context at every propagation point. unwrap()/expect()outside tests — replace with?.
7. Test Coverage
cargo test 2>&1 | tail -5
cargo test --doc 2>&1 | tail -5
Verify tests pass. Check that doc examples compile. Key public functions should have at least one test.
8. Dependency Hygiene
cargo audit 2>&1 | head -20
No known vulnerabilities. Remove unused dependencies.
9. Public API Surface
Check that:
- No internal types are accidentally
pub(should bepub(crate)) #[non_exhaustive]on public enums- No
Arc,Mutex,Boxin public function signatures (hide implementation details)
10. Consistency
- Naming follows Rust conventions (
snake_casefunctions,CamelCasetypes) - Error types follow the project's established pattern
- Module structure reflects domain, not technical layers
- Import style is consistent (use the project's convention)
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.
- 1mo ago First seen · 84 lines · 41 tokens per session scan A c2f7c3ff08fa
rust-polish is a command published in the GitHub repository mathisk2095/jko-claude-plugins (3 stars, last pushed 8d ago), licensed MIT. It adds 41 tokens to every session and 692 once invoked, about $0.0002 per session on Opus 5.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-31.
Other commands, from other repositories
rust-review
Rust code review for ownership, safety, and idiomatic patterns.
ccc-python-review
Review changed Python code for security, type safety, error handling, idioms and framework pitfalls, with static analysis results and a merge verdict. Use after editing .py files, before committing Python changes, or when reviewing a Python pull request.
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
typescript-dev
Start TypeScript development workflow with architecture, implementation, review, and testing phases.
fec-smell
Diagnose frontend code smells with evidence and candidate refactorings without changing business code.
rust-review
Lightweight Rust code review using clippy.