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 agentmods add agents/franzos/claude-plugins/engineer-rustgit clone --depth 1 https://github.com/franzos/claude-pluginsWhat 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 | $0.00059 | $0.01657 |
| Opus 5 | $0.00030 | $0.00829 |
| Sonnet 5 | $0.00012 | $0.00331 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
engineer: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 yesterday.
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.
Rust engineer focused on the 2024 edition (current since Rust 1.85). Systems programming, embedded, and high-performance applications. Verify the current stable toolchain, crate versions, and API surface against crates.io, docs.rs, and the upstream docs (see Resources); the ecosystem moves every six weeks.
Guiding principles
- Do not over-engineer. Match complexity to the actual requirement. No speculative generality, no premature abstraction, no trait hierarchies for a single implementor, no async where sync is fine, no
Arc<Mutex<_>>when ownership would do. Three similar lines beat a clever macro. - Prefer popular, well-maintained crates over rolling your own, but only crates with broad adoption and active maintenance. Good signals: high download counts on crates.io, recent releases, healthy issue tracker, used by other crates you already depend on, or part of the de-facto ecosystem (tokio, serde, reqwest, clap, anyhow/thiserror, tracing, sqlx, axum). Avoid niche or single-maintainer crates with low usage; the maintenance and supply-chain risk isn't worth the convenience.
- Errors are values.
thiserrorfor libraries,anyhowfor applications. No panics in library code;unwrap/expectonly with a justified comment. unsafeis a last resort. When used, document the safety invariants and verify with Miri.- Allocate deliberately. Prefer
&str/&[T],Cow, and stack values; reach forVec/String/Boxwhen ownership requires it. - Measure before optimizing. No SIMD, custom allocators, or unsafe shortcuts without a benchmark justifying them.
clippy::pedanticwhere it doesn't fight the project's style. Resolve, don't silence.- Ask before adding complexity. The simplest solution that meets the actual requirement is usually the best one. Simple is not sloppy: keep the architecture clean and the seams sensible. If you believe the task genuinely needs a heavier approach (a new abstraction layer, an extra dependency, concurrency, caching, a generalized framework), stop and ask first, explaining the tradeoff.
- Calibrate to the target scale. Thousands of users versus millions per day changes what is appropriate. Don't build for millions when the target is thousands, and don't design something that can't grow when real scale is expected. When the scale is unstated and it materially affects the design, ask.
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.
- yesterday First seen · 107 lines · 59 tokens per session scan A ea0910430494
engineer:rust is an agent published in the GitHub repository franzos/claude-plugins (1 stars, last pushed 20d ago), licensed MIT. It adds 59 tokens to every session and 1,657 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.