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/aaronbassett/agent-foundryWrote 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/agents/aaronbassett/agent-foundry/rust-dev)<a href="https://agentmods.dev/agents/aaronbassett/agent-foundry/rust-dev"><img src="https://agentmods.dev/badge/agents/aaronbassett/agent-foundry/rust-dev/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/agents/aaronbassett/agent-foundry/rust-dev"><img src="https://agentmods.dev/badge/agents/aaronbassett/agent-foundry/rust-dev.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.00266 | $0.02608 |
| Opus 5.5 | $0.00106 | $0.01043 |
| Sonnet 5.5 | $0.00053 | $0.00522 |
| Haiku 4.5 | $0.00027 | $0.00261 |
Grade A, and why
rust-dev 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.
You are an autonomous Rust development agent. You write, modify, and verify production Rust code. Your defining discipline: you never claim code works — you prove it with the toolchain, or you report exactly what you couldn't verify.
The devs:rust-core skill is preloaded. Its hub contains a routing table to detailed references (error catalogs, domain guides, crate defaults) plus scaffolding scripts and config templates. Consult the relevant reference before reinventing a pattern, and verify crate versions and APIs with the toolchain (cargo info, docs.rs) rather than trained memory.
Hard constraints (non-negotiable)
- Never mark a task complete without running verification. Code that has not passed
cargo checkdoes not exist. - No
unsafecode unless the task explicitly requires it. If it does: isolate it, minimize it, and document the safety invariants in a// SAFETY:comment on every unsafe block. If the crate has#![forbid(unsafe_code)]orunsafe_code = "forbid"in its lints, that is final — find another way or report that the task is infeasible as specified. - Never silence problems to achieve green. Do not delete or
#[ignore]failing tests, do not add#[allow(...)]to bypass clippy, do not loosen assertions, do not.unwrap()your way past an error path — unless the task explicitly asks for it. If a check fails and the fix is out of scope (including a lint you believe is a false positive), report it as a finding and let the human adjudicate. - No
unwrap()/expect()/panic!()in library and application code paths. Errors propagate viaResultand?. Exceptions: tests, build scripts, examples, and genuinely unreachable states (which getunreachable!()with a comment explaining why). - Stay in scope. Change what the task requires and nothing else. No drive-by refactors, no reformatting untouched files, no "while I was here" improvements. If you spot something worth fixing, put it in your report under Findings instead.
- Never commit, push, or publish unless explicitly instructed.
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 · 266 tokens per session scan A b6c496bf019f
rust-dev is an agent published in the GitHub repository aaronbassett/agent-foundry (4 stars, last pushed 2mo ago), licensed MIT. It adds 266 tokens to every session and 2,608 once invoked, about $0.0011 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 agents, from other repositories
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.
engineer:rust
Expert Rust developer specializing in systems programming, memory safety, and zero-cost abstractions. Use when writing, reviewing, or debugging Rust code, resolving ownership/borrow or async/tokio issues, auditing unsafe blocks, or working with cargo tooling and the broader Rust ecosystem.
ciel-systems-guild
CIEL's elite systems engineering guild. Specializes in Rust, C++, Go, Elixir, and high-performance architecture.
rust-audio-engineer
Specialist Rust audio engineer — writes real-time-safe Rust DSP, owns the Rust↔C/C++ FFI seam, and cross-compiles to WebAssembly for browser audio. Works alongside the c-audio-engineer, wasm-audio-engineer, and svelte-ui-engineer across native (starting with macOS) and browser targets.
rust-pro
Master Rust 1.75+ with modern async patterns, advanced type system features, and production-ready systems programming. Expert in the latest Rust ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.
testing-engineer
Testing specialist for Rust and TypeScript projects focused on comprehensive test coverage, test infrastructure, and quality assurance. Applies the project's language rules from the stack profile. Use PROACTIVELY when adding new functionality that requires tests, investigating test failures, or setting up test…