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/go-1-21-brutal-audit)<a href="https://agentmods.dev/rules/beettlle/pi-spine/go-1-21-brutal-audit"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/go-1-21-brutal-audit/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/beettlle/pi-spine/go-1-21-brutal-audit"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/go-1-21-brutal-audit.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.03552 |
| Opus 5 | $0.00000 | $0.01776 |
| Sonnet 5 | $0.00000 | $0.00710 |
| Haiku 4.5 | $0.00000 | $0.00355 |
Grade A, and why
go-1-21-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 12d 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 — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Brutal Audit Workflow
This rule defines the workflow for conducting a "Brutal Audit" of the Go codebase.
Apply this rule 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. 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: 2.0 (Updated for Go 1.21+, Effective Go, Uber Style Guide)
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/go-1-21-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 imports (check registry)
- No TODO/FIXME in production
- No discarded results (
_ = expensiveOp()) - No I/O in loops (batch operations)
- No >80% delegation methods
- No hardcoded secrets
- No silent failures
- Security (OWASP): see
owasp-secure-coding-practices.mdcfor full checklist
Tool: Use grep to verify before detailed audit.
🔵 PRE-CODE GENERATION: Chain-of-Thought Checkpoints
Before generating code, identify:
- Which layer affected (Domain/Data/Presentation)
- Similar pattern exists? (Check codebase first)
- Framework provides direct API? (Verify docs)
- Ghost layer candidate? (>80% delegation check)
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.
- 12d ago First seen · 479 lines · 0 tokens per session scan A 40bef33932b6
go-1-21-brutal-audit is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,552 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
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
code-review
BMAD BMM Agent: code-review.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.