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 bugrabilge/bilge-development-kit --skill rust-progit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote 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/bugrabilge/bilge-development-kit/rust-pro)<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/rust-pro"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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/bugrabilge/bilge-development-kit/rust-pro"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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.00036 | $0.01841 |
| Opus 5 | $0.00018 | $0.00920 |
| Sonnet 5 | $0.00007 | $0.00368 |
| Haiku 4.5 | $0.00004 | $0.00184 |
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 5d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Pro
"In Rust, the compiler is your strictest code reviewer and your most reliable safety net."
When to Use
- Writing new Rust code or modules
- Reviewing Rust code for idiomatic patterns
- Debugging ownership, borrowing, or lifetime errors
- Implementing async Rust with Tokio or async-std
- Designing concurrent systems with Rust's guarantees
- Choosing between Rust abstractions (trait objects vs. generics, Arc vs. Rc)
Ownership and Borrowing
Core Rules
- Each value has exactly one owner
- When the owner goes out of scope, the value is dropped
- You can have either one mutable reference OR any number of immutable references (not both)
When to Clone vs. Borrow
- Borrow (&T or &mut T) by default; cloning is a last resort, not a first instinct
- Clone when you need independent ownership (e.g., sending data to another thread)
- Clone when the data is small and cheap to copy (small strings, numbers, small structs)
- Use Cow<'_, T> when you sometimes need to own and sometimes need to borrow
Common Ownership Patterns
// Transfer ownership
fn process(data: Vec<u8>) { /* owns data, dropped at end */ }
// Borrow immutably
fn analyze(data: &[u8]) -> usize { data.len() }
// Borrow mutably
fn transform(data: &mut Vec<u8>) { data.push(0); }
// Return owned data
fn create() -> Vec<u8> { vec![1, 2, 3] }
Avoiding Borrow Checker Fights
- Structure code so borrows have clear, non-overlapping scopes
- Split structs if one field's borrow conflicts with another's mutation
- Use indices instead of references into collections you need to mutate
- Consider interior mutability (RefCell, Mutex) when shared mutable state is truly needed
Lifetimes
When Annotations Are Needed
- Function signatures with references in both input and output
- Struct definitions that hold references
- Impl blocks for structs with lifetime parameters
Lifetime Elision Rules
- Each input reference gets its own lifetime parameter
- If there is exactly one input lifetime, it is assigned to all output lifetimes
- If one input is &self or &mut self, its lifetime is assigned to all outputs
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.
- 5d ago First seen · 232 lines · 36 tokens per session scan A de57ccd0f42c
rust-pro is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,841 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
omh-rust
This is a Hermes-native rust workflow skill.
bevy-ecs
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the Time resource for frame-rate-independent motion. Use when building or debugging a Bevy game in Rust — when the user mentions…
rust-project
Modern Rust project architecture guide for 2025. Use when creating Rust projects (CLI, web services, libraries). Covers workspace structure, error handling, async patterns, and idiomatic Rust best practices.
azure-keyvault-secrets-rust
Client library for Azure Key Vault Secrets — secure storage for passwords, API keys, and other secrets.
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.