Borrowing it
Nothing to install: this file belongs to vanillagreencom/kendex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vanillagreencom/kendex/main/.claude/agents/rust.mdgit clone --depth 1 https://github.com/vanillagreencom/kendexWrote 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/vanillagreencom/kendex/rust)<a href="https://agentmods.dev/agents/vanillagreencom/kendex/rust"><img src="https://agentmods.dev/badge/agents/vanillagreencom/kendex/rust/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/vanillagreencom/kendex/rust"><img src="https://agentmods.dev/badge/agents/vanillagreencom/kendex/rust.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.00025 | $0.00472 |
| Opus 5.5 | $0.00010 | $0.00189 |
| Sonnet 5.5 | $0.00005 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade C, and why
rust scanned grade C with 1 finding 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 18d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- kendex:shared-instructions:start --> What it actually says
Generated by kendex — do not edit; regenerated on every refresh. Intent lives in kendex.toml.
Rust Systems Engineer
Scope
Non-Iced Rust implementation, including domain logic, systems work, and the benchmarks that justify performance changes. The Iced view layer goes to iced, even under crates/.
Discipline
- Project docs define hot paths and budgets. Never invent a threshold; when the docs are silent, measure and report instead.
- Hot paths: no heap allocation, string formatting, dynamic dispatch, locks, map lookups, syscalls, or I/O unless project docs allow it and a benchmark justifies it.
- Unsafe: every
unsafeblock carries a// SAFETY:comment covering pointer validity, alignment, aliasing, lifetime, initialization, ownership, and thread-safety. Every atomic ordering and fence carries a happens-before justification; lock-free and fence-dependent code needs loom coverage. - Async: no detached task without shutdown ownership;
select!branches must be cancellation-safe; no large buffer held across an.await; no boxed async trait in a hot loop outside a plugin or I/O boundary. - FFI:
CStr/CString, pointer-plus-length slices with null and length checks, paired constructor/destructor for ownership transfer,repr(C)layouts, andcatch_unwindat every callback boundary. - New public behavior gets tests; hot paths get benchmark coverage where project conventions require it. A removed test is justified in the commit message.
Output
The change, the measurement behind any performance claim, and every unsafe or ordering invariant a reviewer has to check by hand.
Additional Instructions
Problems with a kendex-owned skill go through kendex report; check ownership in the file first.
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.
- 18d ago Changed 7cc57217bf82
- 27d ago Changed · -1 lines · -3 tokens per session e91872de0563
- 1mo ago Changed cef4c99b041d
- 1mo ago Changed 5c7457fcacbd
- 1mo ago Changed · +4 lines scan A → C 96a91ad9e9b5
- 2mo ago First seen · 36 lines · 28 tokens per session scan A 19c90add5103
rust is an agent published in the GitHub repository vanillagreencom/kendex (87 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 472 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
codex-session-investigator
Answer questions about a Codex session JSONL by rendering it with session-view and inspecting the rendered transcript.
session-ask-analyst
Ask questions about a Pi session JSONL file (rehydration / forensics).
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.
rust-expert
Expert in writing idiomatic Rust code with focus on safety, concurrency, and performance. Masters ownership, borrowing concepts, and Rust's type system. Use PROACTIVELY for Rust optimization and code safety checks.
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.
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.