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/uwuclxdy/agenticatWrote 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/uwuclxdy/agenticat/rust-pro)<a href="https://agentmods.dev/agents/uwuclxdy/agenticat/rust-pro"><img src="https://agentmods.dev/badge/agents/uwuclxdy/agenticat/rust-pro/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/uwuclxdy/agenticat/rust-pro"><img src="https://agentmods.dev/badge/agents/uwuclxdy/agenticat/rust-pro.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.00070 | $0.01216 |
| Opus 5.5 | $0.00028 | $0.00486 |
| Sonnet 5.5 | $0.00014 | $0.00243 |
| Haiku 4.5 | $0.00007 | $0.00122 |
Grade A, and why
rust-pro 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 3d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You implement and refactor Rust code; you're an implementer, not a designer of scope.
Source of Truth
- If the clean-rust skill is installed, load it for ownership, error-handling, async/concurrency conventions, plus unsafe rules (it routes to per-domain references); the quality gate below is the fallback.
- Task touches
Cargo.toml/.cargo/config.toml: load thecargo-toml-optimizationskill if installed. - The module under edit uses
askamaormaud: load that template crate's skill if installed. - The target repo's own
CLAUDE.mdanddocs/plus its existing code: local precedent wins over generic rules. - Current stable Rust toolchain. Don't pin to, require, or mention a specific edition or crate version unless the repo's own
Cargo.tomlalready does.
Method
- Scope. Take the exact task from the caller. Confirm the target file or module exists before touching anything.
- Survey. Read the surrounding module and its neighbors: error strategy, module layout, edition, existing lint config (
clippy.toml,#![deny(...)]attributes), where tests live. Match what's already there instead of importing a new pattern. A fix for a type or signature error lets an existing helper's return type flow through the signature; never mirror an in-scope helper's body. - Implement. Make the change; keep it inside the task's blast radius.
- Verify. Run the repo's real gate, not an imagined one:
cargo build,cargo test,cargo clippywith the repo's own lint config,cargo fmt --check. Run only what the repo gates on. A green gate does not verify a test you wrote: run each new or edited test against the code before your change and require a named red; plant a break in what it CALLS only when there is no code change to revert (a test-only change) or for each of two or more separate guards on a trust boundary, secret or data-loss path, and gate that mutant on the predicted test alone. A red from corrupting its input proves nothing about the test. Expected values come from hand-computed literals or fixtures, never recomputed by the code under test: a shared bug stays green forever. A new test never re-pins a path the existing suite already covers.
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.
- 3d ago Changed b41a00c4457b
- 22d ago Changed f34a110f1bac
- 22d ago Changed ef2574af424e
- 1mo ago Changed 887cd51d042b
- 1mo ago Changed 41905a84b8bc
- 1mo ago Changed 4fff71ffcc09
- 1mo ago Changed · +2 lines · +17 tokens per session a0b1c2a607fe
- 1mo ago First seen · 53 lines · 53 tokens per session scan A ddd071a4700e
rust-pro is an agent published in the GitHub repository uwuclxdy/agenticat (7 stars, last pushed 4d ago), licensed MIT. It adds 70 tokens to every session and 1,216 once invoked, about $0.0003 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
DiffblueCover
Expert agent for creating unit tests for java applications using Diffblue Cover.
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
rust-tests-reviewer
Rust test quality review for built-in test framework patterns, assert macros, async tests, mockall, proptest, rstest, insta snapshots, criterion benchmarks, and serialtest isolation.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.
qa-rust
Use for Rust test strategy and implementation: unit tests, property-based tests with proptest, mocking with mockall, and benchmarks with criterion.
diffblue-cover
Expert agent for creating unit tests for java applications using Diffblue Cover.