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/maxgfr/conformeWrote 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/maxgfr/conforme/rust-conventions)<a href="https://agentmods.dev/rules/maxgfr/conforme/rust-conventions"><img src="https://agentmods.dev/badge/rules/maxgfr/conforme/rust-conventions/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/rules/maxgfr/conforme/rust-conventions"><img src="https://agentmods.dev/badge/rules/maxgfr/conforme/rust-conventions.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.00000 | $0.00219 |
| Opus 5.5 | $0.00000 | $0.00088 |
| Sonnet 5.5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
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 4d 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
- Run
cargo clippy --all-targets -- -D warningsbefore considering any change complete - Run
cargo testafter modifying adapter logic, MCP generation, or skills generation - Use
anyhow::Resultfor fallible functions,anyhow::Contextfor error messages - Use
BTreeMap(notHashMap) for deterministic output ordering in generated files - Parse frontmatter fields defensively: use
.and_then(|v| v.as_str())chains, never.unwrap()on user input - When parsing tool-separated lists (e.g.
allowed-tools,tools), useskills::parse_frontmatter_tool_list: it handles space- and comma-separated strings and YAML lists, and keepsBash(git add:*)whole - Keep adapter
read()andgenerate()symmetric: ifgenerate()writes a field,read()must parse it back correctly (round-trip guarantee)
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.
- 4d ago Changed fafe7e67fc17
- 1mo ago First seen · 14 lines · 0 tokens per session scan A 7d80223be3a3
rust-conventions is a cursor rule published in the GitHub repository maxgfr/conforme (3 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 219 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-31.
Other cursor rules, from other repositories
cursor-project-rule
Project Spine operating contract for "Ledger API".
project-spine-apps-web
Project Spine scoped guidance for "apps/web".
project-spine-packages-ui
Project Spine scoped guidance for "packages/ui".
typescript
TypeScript conventions.
rust
Rust patterns: ownership, Result types, iterators.
hatch3r-rust-patterns
Rust conventions covering 2024 edition idioms, error handling with thiserror/anyhow, ownership patterns, async with Tokio, testing, and Cargo workspaces.