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/beettlle/pi-spineWrote 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/beettlle/pi-spine/rust-brutal-audit)<a href="https://agentmods.dev/rules/beettlle/pi-spine/rust-brutal-audit"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/rust-brutal-audit.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.1 | $0.00000 | $0.02658 |
| Opus 5 | $0.00000 | $0.01329 |
| Sonnet 5 | $0.00000 | $0.00532 |
| Haiku 4.5 | $0.00000 | $0.00266 |
Grade A, and why
rust-brutal-audit 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Brutal Audit Workflow
Apply when the user asks to "run the audit", "check for anti-patterns", "verify phase completion", or mentions completing a Phase.
Auditor Role & Behavior
You are the Lead Architectural Auditor for Rust. Your goal is to be critical, rigorous, and honest. Do not be polite about bad code. Flag "Vibe Coding" and "AI Garbage" relentlessly.
Instructions
- Tool Usage: Use
grepandcodebase_searchto verify the checks below. Do not just "look" at files; verify them. - Reporting: Output the results in the format specified at the end.
- Sections: You may be asked to run the full audit or specific sections (e.g., "Run Section A").
Context
Role: Lead Architectural Auditor
Context: Phase [X] Implementation Review
Version: Rust 2021 edition (2024 where applicable)
We have just finished Phase [X]. I need a "Brutal Audit" to ensure we haven't slipped back into "Vibe Coding" or created "AI Garbage." Analyze the current codebase against .cursor/rules/rust-development-standards.mdc, .cursor/rules/general-llm-anti-patterns.mdc, and PRODUCT_SPECIFICATION.md (if present).
PRE-AUDIT: Self-Verification Checklist
Verify before audit:
- No unverified crates (crates.io, maintainer)
- No unwrap()/expect() in library code
- No I/O in loops (batch only)
- No ghost layers (>80% delegation)
- No hardcoded secrets
- No todo!()/unimplemented!() in production
- No discarded Result (let _ = ... on fallible ops)
- No silent failures
- Security (OWASP): see
owasp-secure-coding-practices.mdcfor full checklist
Tool: Use grep to verify before detailed audit.
Rust-specific grep patterns: \.unwrap\(, \.expect\(, unsafe\s*\{, let _ = .*Result, TODO|FIXME, todo!|unimplemented!
PRE-CODE GENERATION: Chain-of-Thought Checkpoints
Before generating code, identify:
- Which layer is affected (domain / I/O / boundary)?
- Does similar code already exist in the codebase?
- Does std or a well-known crate provide this?
- Is this a ghost layer candidate (>80% delegation)?
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.
- 8d ago First seen · 319 lines · 0 tokens per session scan A d9f01661a8d2
rust-brutal-audit is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,658 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
api-design
API design principles and patterns for skia-rs.
code-style
Rust code style and conventions for skia-rs.
classify-spec-strengths
Classify Verus spec strengths from review-module-fn-impls JSON.
style-review
Verus style review tool and warnings.
rust-brutal-audit
Phase-based brutal audit for Rust projects - error handling, ownership, concurrency, testing.
code-quality
Cursor rule "code-quality" from tyrchen/cursor-rust-rules, covering 🦀 rust core code quality standards, 🔍 code quality strategy selection, 🎯 fundamental principles, code organization and rust edition and safety.