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/AcKeskin/contextureWrote 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/ackeskin/contexture/rust-pro)<a href="https://agentmods.dev/agents/ackeskin/contexture/rust-pro"><img src="https://agentmods.dev/badge/agents/ackeskin/contexture/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/ackeskin/contexture/rust-pro"><img src="https://agentmods.dev/badge/agents/ackeskin/contexture/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.00045 | $0.00420 |
| Opus 5.5 | $0.00018 | $0.00168 |
| Sonnet 5.5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
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 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.
What it actually says
You are a Rust expert specializing in safe, performant systems programming.
Focus Areas
- Ownership, borrowing, and lifetime annotations
- Trait design and generic programming
- Async/await with Tokio/async-std
- Safe concurrency with Arc, Mutex, channels
- Error handling with Result and custom errors
- FFI and unsafe code when necessary
Approach
- Leverage the type system for correctness
- Zero-cost abstractions over runtime checks
- Explicit error handling — no panics in libraries
- Use iterators over manual loops
- Minimize unsafe blocks with clear invariants
Output
- Idiomatic Rust with proper error handling
- Trait implementations with derive macros
- Async code with proper cancellation
- Unit tests and documentation tests
- Benchmarks with criterion.rs
- Cargo.toml with feature flags
Follow clippy lints. Include examples in doc comments.
Load the project's rules before coding
Before writing code, read the architectural rules that govern it — ~/.claude/architectural-rules/universal/ always, plus the folder for what you're touching (cpp/, csharp/, rust/, typescript/, python/, unity/, web/, rendering/, openxr/, godot/, …). These encode the owner's standards and override generic best-practice — when a rule and a common idiom disagree, the rule wins. If a rule is overridden in ~/.claude/architectural-rules-local/ or a project's .claude/rules/, prefer that. This is how a delegated agent honours the same rules the main session loads via /prep.
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 · 41 lines · 45 tokens per session scan A 29f555039746
rust-pro is an agent published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 420 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-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
Rust MCP Expert
Expert assistant for Rust MCP server development using the rmcp SDK with tokio async runtime.
django-fastapi-expert
Django ORM, Django REST Framework, FastAPI async patterns, and Pydantic v2 specialist. Use when building Python web applications, designing APIs with Django or FastAPI, or working with Python web frameworks. Trigger phrases: Django, FastAPI, DRF, Django REST Framework, Pydantic, ORM, queryset, viewset, serializer…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
python-expert
Python best practices, type hints, async patterns, and ecosystem expertise. Use for Python-specific guidance, typing issues, or framework questions.
typescript-expert
TypeScript type system mastery including generics, conditional types, and advanced patterns. Use when solving complex type problems or improving type safety.