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 shahidshabbir-se/my-pi-setup --skill rustgit clone --depth 1 https://github.com/shahidshabbir-se/my-pi-setupWrote 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/shahidshabbir-se/my-pi-setup/rust)<a href="https://agentmods.dev/skills/shahidshabbir-se/my-pi-setup/rust"><img src="https://agentmods.dev/badge/skills/shahidshabbir-se/my-pi-setup/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/shahidshabbir-se/my-pi-setup/rust"><img src="https://agentmods.dev/badge/skills/shahidshabbir-se/my-pi-setup/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.00016 | $0.00384 |
| Opus 5 | $0.00008 | $0.00192 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
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 10d 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.
This is a copy
100% identical to rust — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Rust
You are an expert in Rust development with deep knowledge of systems programming, memory safety, and async patterns.
Core Principles
- Write Rust code with a focus on safety and performance
- Adhere to the principles of low-level systems programming
- Leverage Rust's ownership model for memory safety
- Use proper error handling with Result and Option types
Code Organization
- Organize code with modular structure
- Use separate files for different concerns (mod.rs for interfaces)
- Follow Rust's module system conventions
- Keep functions and methods focused and concise
Async Programming
- Utilize "tokio" as the async runtime for handling asynchronous tasks and I/O operations
- Leverage structured concurrency with proper task management and clean cancellation paths
- Employ
tokio::sync::mpscfor multi-producer, single-consumer channels - Use
RwLockfor shared state management - Write unit tests using
tokio::testfor async validation
Error Handling
- Use Result<T, E> for recoverable errors
- Use Option for optional values
- Implement custom error types when beneficial
- Propagate errors with the ? operator
- Provide meaningful error messages
Performance
- Prefer stack allocation over heap when possible
- Use references to avoid unnecessary cloning
- Leverage zero-cost abstractions
- Profile code to identify bottlenecks
- Use iterators for efficient data processing
Testing
- Write comprehensive unit tests
- Use Quickcheck for property-based testing
- Test async code with appropriate test macros
- Implement integration tests for end-to-end validation
Security
- Implement strict access controls
- Validate all inputs thoroughly
- Conduct regular vulnerability audits
- Follow security best practices for data handling
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.
- 10d ago First seen · 61 lines · 16 tokens per session scan A 859bb577ffba
rust is a skill published in the GitHub repository shahidshabbir-se/my-pi-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 384 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to rust, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
rust-crate-ci
Load before editing any Rust crate in this repo (currently runners/swarm-sandbox-runner). Covers the mandatory local validation gate, common rustfmt/clippy pitfalls, and Windows-specific Rust correctness patterns that CI enforces but are hard to catch locally without a Windows toolchain.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
ios-development
Comprehensive guide for building native Apple platform applications.
kotlin-multiplatform
KMP/CMP shared business logic, Compose Multiplatform, expect/actual, Ktor, SQLDelight, and platform-specific implementations. Use when building cross-platform Kotlin applications for Android, iOS, desktop, or web.
writing-rust
Idiomatic Rust development. Use when writing Rust code, Cargo crates/workspaces, Rust tests, or rustfmt/clippy/cargo workflows. Emphasizes ownership, Result errors, small APIs, stdlib-first dependencies, fast cargo feedback, and behavior tests. NOT for Go, Python, TypeScript, shell scripts, or infra-only work.