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 skills add qte77/claude-code-plugins --skill implementing-rustgit clone --depth 1 https://github.com/qte77/claude-code-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/skills/qte77/claude-code-plugins/implementing-rust)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/implementing-rust"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/implementing-rust/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/qte77/claude-code-plugins/implementing-rust"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/implementing-rust.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.00037 | $0.00410 |
| Opus 5.5 | $0.00015 | $0.00164 |
| Sonnet 5.5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
implementing-rust 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 23d 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.
What it actually says
Rust Implementation
Target: $ARGUMENTS
Creates focused, streamlined Rust implementations following architect specifications exactly. No over-engineering.
Rust Standards
See references/rust-best-practices.md for comprehensive Rust guidelines.
Workflow
- Read architect specifications from provided documents
- Validate scope — Simple (single module) vs Complex (multi-module)
- Study existing patterns in
src/structure - Implement minimal solution matching stated functionality
- Create focused tests matching task complexity
- Run validation and fix all issues
Implementation Strategy
Simple Tasks: Single module, minimal structs, thiserror errors, inline tests
Complex Tasks: Multi-module with traits, async with tokio, custom error types, integration tests
Always: Use existing project patterns, pass validation
Output Standards
Simple Tasks: Minimal functions with proper error handling Complex Tasks: Complete modules with traits, tests, and documentation All outputs: Concise, streamlined, no unnecessary complexity
Quality Checks
Before completing any task:
cargo test && cargo clippy -- -D warnings && cargo fmt --check
All tests, lints, and formatting must pass.
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.
- 23d ago Changed · +1 lines f10eca77f8f0
- 1mo ago First seen · 54 lines · 37 tokens per session scan A e11983ed38fa
implementing-rust is a skill published in the GitHub repository qte77/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 410 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
rust-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting Rust code. Detects edition and toolchain from the project. Provides expert critique covering ownership, error handling, unsafe review, async correctness, trait design, type system patterns, performance, SOLID principles, and…
android-kotlin-compose
Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…
android-kotlin-coroutines
Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…
cloudflare-workers-multi-lang
Multi-language Workers development with Rust, Python, and WebAssembly. Use when building Workers in languages other than JavaScript/TypeScript, or when integrating WASM modules for performance-critical code.
dotnet-analyzers
Run dotnet format to fix code style and analyzer diagnostics (IDE0005, CA, SA). Use when fixing unnecessary usings, code style violations, analyzer warnings, or verifying format compliance.
dotnet-test
This skill should be used when running .NET tests selectively with a build-first, test-targeted workflow. Use it for running tests with xUnit focus.