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 Dicklesworthstone/remote_compilation_helper --skill rust-error-handlinggit clone --depth 1 https://github.com/Dicklesworthstone/remote_compilation_helperWrote 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/dicklesworthstone/remote_compilation_helper/rust-error-handling)<a href="https://agentmods.dev/skills/dicklesworthstone/remote_compilation_helper/rust-error-handling"><img src="https://agentmods.dev/badge/skills/dicklesworthstone/remote_compilation_helper/rust-error-handling.svg" alt="Measured on agentmods" 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.00027 | $0.00423 |
| Opus 5 | $0.00014 | $0.00211 |
| Sonnet 5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
Rust Error Handling 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 8d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 8d ago First seen · 64 lines · 27 tokens per session scan A f732c12fa0a8
Rust Error Handling is a skill published in the GitHub repository Dicklesworthstone/remote_compilation_helper (59 stars, last pushed today), with no licence file. It adds 27 tokens to every session and 423 once invoked, about $0.0001 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 Error Handling
Rust-specific error handling patterns, building on the base error handling skill. Demonstrates the 'extends' composition feature.
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.
Error Handling Base
Foundation for error handling patterns. This is a base skill designed to be extended by language-specific error handling skills.
Rust Patterns
Use this skill when writing Rust crates/services and you want reliable patterns for error handling, module structure, ownership boundaries, and maintainable APIs.
rust-check
Run cargo check on the current Rust project to find compile errors.
printing-press-polish
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use…