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.
git clone --depth 1 https://github.com/mfmezger/ai_agent_dotfilesWrote 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/commands/mfmezger/ai_agent_dotfiles/rust-engineering)<a href="https://agentmods.dev/commands/mfmezger/ai_agent_dotfiles/rust-engineering"><img src="https://agentmods.dev/badge/commands/mfmezger/ai_agent_dotfiles/rust-engineering/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/commands/mfmezger/ai_agent_dotfiles/rust-engineering"><img src="https://agentmods.dev/badge/commands/mfmezger/ai_agent_dotfiles/rust-engineering.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.00117 | $0.00951 |
| Opus 5.5 | $0.00047 | $0.00380 |
| Sonnet 5.5 | $0.00023 | $0.00190 |
| Haiku 4.5 | $0.00012 | $0.00095 |
Grade A, and why
rust-engineering 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Engineering
Produce Rust that is safe, explicit, and maintainable under review. Default to stable language features, minimal unsafe, narrow APIs, and code that passes formatting, linting, and tests.
Workflow
- Identify the artifact. Library: optimize for explicit API boundaries, typed errors, docs, and semver-safe design. Application or CLI: optimize for operability, context-rich errors, tracing, and clear failure modes.
- Model types before writing control flow. Prefer enums, newtypes, and private fields over ad hoc strings, flags, or loosely related values.
- Choose ownership deliberately. Accept borrowed inputs where practical, return owned outputs when crossing boundaries, and make cloning explicit.
- Choose the failure model early.
Libraries usually use
thiserror; applications usually useanyhowat the outer boundary and typed errors internally when helpful. - Choose the concurrency model deliberately. Use synchronous code unless async is justified by I/O concurrency needs. When async is justified, use Tokio and design cancellation, timeouts, and shutdown explicitly.
- Verify before finalizing.
Run
cargo fmt --check,cargo clippy --all-targets --all-features, and relevant tests. Address warnings instead of normalizing them.
Load References By Need
| Need | Reference |
|---|---|
| Project setup, crate structure, CLI patterns, tracing | references/workflow.md |
Error model, thiserror vs anyhow, context, path/file failure handling |
references/errors.md |
| Ownership, API boundaries, newtypes, traits, visibility, serde-facing types | references/api-and-types.md |
| Tokio, cancellation, timeouts, shared state, task spawning, async traits | references/async-and-concurrency.md |
| Unit/integration/doc/property tests, benchmarks, temp files, review checklist | references/testing-and-quality.md |
Allocation control, data layout, slices, Cow, boxing, profiling |
references/performance-and-memory.md |
| Common footguns and review traps | references/footguns.md |
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 · 69 lines · 117 tokens per session scan A 75dfc763a9c5
rust-engineering is a command published in the GitHub repository mfmezger/ai_agent_dotfiles (7 stars, last pushed 3mo ago), licensed MIT. It adds 117 tokens to every session and 951 once invoked, about $0.0005 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-08-31.
Other commands, from other repositories
cargo-metadata
Command "cargo-metadata" from olorehq/olore, covering cargo-metadata(1), name, synopsis, description and output format.
mutation-test
Uses cargo-mutants to run mutation tests and verify test quality.
cargo-build
Command "cargo-build" from olorehq/olore, covering cargo-build(1), name, synopsis, description and options.
cargo-check
Command "cargo-check" from olorehq/olore, covering cargo-check(1), name, synopsis, description and options.
cargo-fetch
Command "cargo-fetch" from olorehq/olore, covering cargo-fetch(1), name, synopsis, description and options.
cargo-new
Command "cargo-new" from olorehq/olore, covering cargo-new(1), name, synopsis, description and options.