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 AmariahAK/atlarix-skills --skill rustgit clone --depth 1 https://github.com/AmariahAK/atlarix-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/amariahak/atlarix-skills/rust)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/rust"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/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/amariahak/atlarix-skills/rust"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/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.00002 | $0.00422 |
| Opus 5.5 | $0.00001 | $0.00169 |
| Sonnet 5.5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
Rust Patterns 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.
What it actually says
Rust Patterns
When to use this skill
Use this skill when writing Rust crates/services and you want reliable patterns for error handling, module structure, ownership boundaries, and maintainable APIs.
Core patterns
Prefer Result/Option over panics
Panics are for programmer bugs, not expected failures.
Pattern:
- return
Result<T, E>from fallible functions - use
thiserror/anyhowdepending on library vs app
Error context matters
When bubbling errors, add context at boundaries:
- IO
- parsing
- network
Ownership boundaries
Prefer:
- passing references
&Twhere possible - cloning only when it improves clarity or lifetimes become complex
Module layout
Common:
src/lib.rsfor librarysrc/main.rsfor binarysrc/<module>.rsorsrc/<module>/mod.rs
Testing
Patterns:
- unit tests in module files
- integration tests in
tests/ - avoid relying on global state
Atlarix tool notes
- Explore: scan
Cargo.tomland entry points (main.rs,lib.rs). - Build: run
cargo testandcargo clippyif configured. - Debug: minimize repro; use feature flags intentionally.
- Review: check error boundaries and public API clarity.
Common mistakes to avoid
- Using panics for expected failures
- Exposing internal types publicly without intent
- Overusing
Rc<RefCell<...>>instead of redesigning ownership
Mini-checklist
- Fallible functions return
Result - Errors have context
- Public API is intentional
- Tests cover error paths
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 · 64 lines · 2 tokens per session scan A f424b1e6bf3f
Rust Patterns is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2 tokens to every session and 422 once invoked, about $0.0000 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-systems
Rust patterns for CLI tools, backend services, and general application code. Use when working with Rust, Cargo workspaces, axum/tokio services, clap CLIs, async concurrency, or configuring clippy, rustfmt, cargo-nextest, or Cargo.toml.
software-engineer-rust
Use when implementing or modifying Rust applications, crates, services, or tests.
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".
azure-eventhub-rust
Client library for Azure Event Hubs — big data streaming platform and event ingestion service.
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.
axum
Builds HTTP APIs and web services in Rust with Axum, the Tokio team's web framework on top of Tokio, Hyper and Tower. Use when a user asks to create a Rust REST API, add routes, extractors, JSON handlers, shared state, middleware, error handling, WebSockets, graceful shutdown or tests with Axum, or to migrate older…