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/uwuclxdy/agenticat/rust-progit clone --depth 1 https://github.com/uwuclxdy/agenticatWhat 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.00053 | $0.00921 |
| Opus 5 | $0.00026 | $0.00461 |
| Sonnet 5 | $0.00011 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
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 — 53 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. - 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: if the change adds or edits a test, break what that test CALLS and require a named red, since a red from corrupting its input proves nothing about it.
Quality Gate
- Ownership and borrow clarity over reflexive
.clone(). - Typed errors (
thiserror) inside library code;anyhowonly at the binary boundary. - No
.unwrap()/.expect()outside tests unless the invariant that makes it safe is commented at the call site. unsafeonly with aSAFETY:comment naming the invariant it upholds.- Async correctness: no blocking call inside an async fn;
Send/Syncbounds reflect what the type guarantees, not what silences the compiler.
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 First seen · 53 lines · 53 tokens per session scan A ddd071a4700e
rust-pro is an agent published in the GitHub repository uwuclxdy/agenticat (5 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 921 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
rust-agent
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
rust-expert
Use this agent when you need expert Rust development, code review, architecture decisions, or optimization work. This includes writing new Rust code, reviewing existing implementations, debugging complex issues, optimizing performance, ensuring memory safety, or making architectural decisions in Rust projects. The…
rust-systems-developer
Rust with cargo + clippy + miri discipline.
dnp-test-writer
🧪 TDD agent for .NET — generates xUnit/NUnit tests with proper mocking, WebApplicationFactory integration tests, and convention-aware assertions.
go-tester
Write concise, resilient, idiomatic Go tests using the stdlib testing package with table-driven patterns. Use when asked to test Go code, write Go tests, add Go test coverage, verify a Go module or package, lock a Go bug with a regression test, or after Go implementation changes need test coverage. Also use when the…
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use for Rust memory safety, performance optimization, or systems programming.