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 jscraik/Agent-Skills --skill rust-progit clone --depth 1 https://github.com/jscraik/Agent-SkillsWrote 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/jscraik/agent-skills/rust-pro)<a href="https://agentmods.dev/skills/jscraik/agent-skills/rust-pro"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/rust-pro/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/jscraik/agent-skills/rust-pro"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/rust-pro.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.00655 |
| Opus 5.5 | $0.00015 | $0.00262 |
| Sonnet 5.5 | $0.00007 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
rust-pro 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Table of Contents
- When to use
- Required inputs
- Deliverables
- Ownership Rules
- Error Handling
- Examples
- Failure mode
- Gotchas
When to use
- Use for Rust implementation or review work.
- Use when correctness, safety, and performance all matter.
Required inputs
- Target crate/module.
- Borrowing/ownership constraints.
- Error semantics and runtime expectations.
Deliverables
- Safe and idiomatic Rust updates.
- Explicit error propagation.
- Notes on any performance-sensitive decisions.
Ownership Rules
- Prefer borrowing over cloning in hot paths.
- Use iterators before indexing loops when possible.
- Keep lifetimes implicit unless explicit annotations improve clarity.
Error Handling
- Prefer
Result<T, E>for recoverable paths. - Use domain-specific error enums over stringly-typed errors.
- Attach context when propagating errors.
Examples
pub fn parse_port(value: &str) -> Result<u16, String> {
value.parse::<u16>().map_err(|_| format!("invalid port: {value}"))
}
Failure mode
- If ownership requirements conflict, favor correctness and simplify data flow.
Gotchas
- Overusing
clone()can hide unnecessary allocations.
See Also
| Skill | When to use |
|---|---|
| [[go]] | Systems programming with similar error-handling and concurrency patterns |
| [[he-fix-bugs]] | Triage Rust ownership and borrow-checker errors with evidence-first diagnosis |
Topic map: [[agent-ops]]
Philosophy
- Optimize for clear, verifiable outcomes with the minimum necessary changes.
- Keep guidance deterministic so repeated runs produce consistent decisions.
Procedure
- Confirm scope, constraints, and required inputs before edits.
- Apply focused changes tied directly to the requested outcome.
- Re-run the highest-signal validations and capture concrete evidence.
Validation
What ships with it
4 files 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.
- 1mo ago First seen · 107 lines · 37 tokens per session scan A b63f8cf902c5
rust-pro is a skill published in the GitHub repository jscraik/Agent-Skills (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 655 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
Rust engineering standards and deep references — ownership/borrowing-driven design, error handling (thiserror/anyhow), async with tokio, axum services, testing, and clippy/cargo-deny discipline. Load whenever writing, editing, or reviewing Rust: any .rs file, Cargo.toml/Cargo.lock change, cargo or clippy failure, or…
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
rust-engineer
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or…
azure-eventhub-rust
Azure Event Hubs library for Rust. Send and receive events for streaming data ingestion and batch processing. Triggers: "event hubs rust", "ProducerClient rust", "ConsumerClient rust", "send event rust", "streaming rust", "eventhub rust".
apollo-router-plugin-creator
Guide for writing Apollo Router native Rust plugins. Use this skill when: (1) users want to create a new router plugin, (2) users want to add service hooks (routerservice, supergraphservice, executionservice, subgraphservice), (3) users want to modify an existing router plugin, (4) users need to understand router…
azure-eventhub-rust
Client library for Azure Event Hubs — big data streaming platform and event ingestion service.