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/timequity/pluginsWrote 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/timequity/plugins/rust-developer)<a href="https://agentmods.dev/agents/timequity/plugins/rust-developer"><img src="https://agentmods.dev/badge/agents/timequity/plugins/rust-developer/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/timequity/plugins/rust-developer"><img src="https://agentmods.dev/badge/agents/timequity/plugins/rust-developer.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.00056 | $0.00820 |
| Opus 5.5 | $0.00022 | $0.00328 |
| Sonnet 5.5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
rust-developer 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 109 lines · 56 tokens per session scan A 7851074fddf6
rust-developer is an agent published in the GitHub repository timequity/plugins (6 stars, last pushed 10mo ago), with no licence file. It adds 56 tokens to every session and 820 once invoked, about $0.0002 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
rust-implementer
Rust TDD implementer worker. Makes a frozen failing test suite pass with the smallest idiomatic change; forbidden from modifying test files. Half of the adversarial Rust fix pair (with rust-test-author). Use when implementing Rust code against frozen tests.
rust-test-author
Rust TDD test-author worker. Writes failing tests against a provided spec/acceptance criteria and freezes them on commit; forbidden from writing implementation code. Half of the adversarial Rust fix pair (with rust-implementer). Use when a Rust change needs tests authored before implementation.
tdd-rust-watcher
Use this agent when the user wants to develop Rust code using strict Test-Driven Development (TDD) methodology with a file watcher. This agent should be used proactively during any Rust development session where TDD is appropriate, including:\n\n \nContext: User is starting work on a new Rust feature\nuser: "I need to…
tdd-rust-engineer
Use this agent when you need to implement Rust projects following strict Test-Driven Development (TDD) practices and clean code principles. Examples include: building CLI tools, implementing domain logic with comprehensive test coverage, creating modular architectures with proper separation of concerns, or when you…
rust-testing-engineer
Rust testing specialist focused on comprehensive test coverage with nextest and criterion, test infrastructure, and quality assurance. Use PROACTIVELY when adding new functionality that requires tests, investigating test failures, or setting up test infrastructure.
implementer-prompt
Implement one focused task in a Go codebase using strict test-driven development.