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/Luxvil/ai-coding-rulesWrote 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/luxvil/ai-coding-rules/64-stack-rust)<a href="https://agentmods.dev/rules/luxvil/ai-coding-rules/64-stack-rust"><img src="https://agentmods.dev/badge/rules/luxvil/ai-coding-rules/64-stack-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/rules/luxvil/ai-coding-rules/64-stack-rust"><img src="https://agentmods.dev/badge/rules/luxvil/ai-coding-rules/64-stack-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.00000 | $0.00073 |
| Opus 5.5 | $0.00000 | $0.00029 |
| Sonnet 5.5 | $0.00000 | $0.00015 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
64-stack-rust 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.
This is a copy
100% identical to 64-stack-rust — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Rust Rules
Safety & Ownership
- Prefer explicit lifetimes only when needed.
- Avoid unnecessary
unsafe.
Style
- Follow
rustfmtdefaults. - Keep functions small and cohesive.
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 · 17 lines · 0 tokens per session scan A 8e59b9b43638
64-stack-rust is a cursor rule published in the GitHub repository Luxvil/ai-coding-rules (3 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 73 tokens. A static security scan graded it A with 0 findings. It is 100% identical to 64-stack-rust, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
code-patterns
Rules for component structure, import patterns using @/ path aliases (never relative paths), import ordering, and TypeScript conventions.
virtual-environment
Rules for using Python virtual environments - check requirements.txt for installed libraries and use the existing virtual environment directory.
hatch3r-rust-patterns
Rust conventions covering 2024 edition idioms, error handling with thiserror/anyhow, ownership patterns, async with Tokio, testing, and Cargo workspaces.
exam-answer-format
Guidelines for writing exam-style answers in a practical, conversational style with definitions first followed by real-world examples.
lecture-reference-linking
Guidelines for including course materials lists and inline references when writing exam answers or documentation that references course materials.
mermaid-diagrams
Guidelines for adding Mermaid diagrams to exam answers and documentation with automatic SVG generation support.