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 rules/c9r-io/orchestrator/rust-conventionsgit clone --depth 1 https://github.com/c9r-io/orchestratorWrote 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/rules/c9r-io/orchestrator/rust-conventions)<a href="https://agentmods.dev/rules/c9r-io/orchestrator/rust-conventions"><img src="https://agentmods.dev/badge/rules/c9r-io/orchestrator/rust-conventions.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00234 |
| Opus 5 | $0.00000 | $0.00117 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
rust-conventions 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.
What it actually says
Rust Conventions (Service Development)
Apply these rules if the backend is Rust under core/.
Structure
- Keep HTTP/gRPC handlers thin.
- Put business logic in
service/with dependency injection via traits. - Keep domain models in
domain/with validation and invariants. - Repositories provide persistence behind mockable traits.
Error Handling
- Use typed errors for business logic (
thiserror), and attach context at boundaries (anyhoworeyre). - Do not swallow errors (
ok()/unwrap()in production paths). - Prefer returning
Result<T, E>from functions instead of side effects.
Async
- Avoid
tokio::spawnunless you can explain lifecycle and error handling. - Prefer explicit timeouts at network boundaries.
Testing
- Unit tests should not require Docker.
- Mock repositories with
mockalland mock HTTP dependencies withwiremock. - Integration/E2E tests can use docker-compose, but keep them separate from unit tests.
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 · 35 lines · 0 tokens per session scan A e71aa652855b
rust-conventions is a cursor rule published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 234 tokens. 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-30.
Other cursor rules, from other repositories
rust-cli-conventions
Conventions for the CLI/TUI, provider abstraction, tool safety, and agent loop.
rust-native-architecture
Enforces native-first architecture and crate boundary rules for the nca workspace.
rust
Rust coding conventions for ralph-core and src-tauri.
axum
Comprehensive best practices for Axum 0.8+ development with WebSocket support.
rust-architect
PoolAI — Rust Architect workflow: runtime stack, MSYS2, target/ disk, pre-push checks, docs sync.
rust-module-refactor
Use when splitting Rust modules, moving tests, tightening visibility, or preserving facades during refactors.