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/golid-ai/golidWrote 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/golid-ai/golid/audit-codebase)<a href="https://agentmods.dev/rules/golid-ai/golid/audit-codebase"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/audit-codebase/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/golid-ai/golid/audit-codebase"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/audit-codebase.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.00021 | $0.02046 |
| Opus 5.5 | $0.00008 | $0.00818 |
| Sonnet 5.5 | $0.00004 | $0.00409 |
| Haiku 4.5 | $0.00002 | $0.00205 |
Grade A, and why
audit-codebase 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Audit Checklist
Thesis: Score the codebase across 7 categories with exact file citations. Check ADRs before flagging documented design decisions.
Run this checklist for release readiness audits. Cite exact file paths and line numbers for every finding. Check docs/adr/ for ADRs before flagging documented design decisions.
Core patterns (apperror, parameterized SQL, batch(), Switch/Match, createResource, alive guard) — see codebase-standards. Frontend fetch — solidjs-data-fetching. Route UI — solidjs-pages.
Backend
- All SQL uses $N parameterized placeholders (no fmt.Sprintf with values or identifiers)
- No
_ = fn()discarded errors in production code - No
echo.NewHTTPErrorin production code (use apperror) - Token refresh is transactional and TOCTOU-safe (atomic UPDATE...RETURNING)
- Password reset uses SELECT...FOR UPDATE inside transaction
- Verification tokens hashed with selector/verifier pattern
- All
rows.Next()loops checkrows.Err()after iteration - JWT_SECRET rejects CHANGE_ME placeholder at startup
- Production entrypoint exits on migration failure
- Timeout middleware uses Echo's built-in (no custom goroutine race)
- All operational constants in Config struct with env var overrides
- ForgotPassword/ResendVerification log errors server-side (anti-enumeration: always return 200)
Frontend
- Zero
createResource— use onMount + signals (seesolidjs-data-fetching) - Zero nested
<Show>for content states — useSwitch/Match(seesolidjs-pages) - Zero
window.confirm()— useDestructiveModal(seesolidjs-pages) - Zero onMount/createEffect cleanup returns — use
onCleanup(seesolidjs-data-fetching) - Zero
anyin production — useunknown(e.g.Record<string, unknown>) - Auth store reacts to
auth:session-expiredwhen token cleared - Auth cookie
Secureon HTTPS set and clear paths - Skip link present with correct target and
tabindex - Auth guard effects use
on()without defer (seesolidjs-pages) -
batch()wraps signal updates after everyawait(seesolidjs-data-fetching)
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 · 136 lines · 21 tokens per session scan A 7393475c1b60
audit-codebase is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 2,046 once invoked, about $0.0001 per session on Opus 5.5. 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
clean-code-skill
Based on Robert C. Martin (Clean Code) and enforced by SonarCloud. For the full reference, see the clean-code skill under .agents/skills/clean-code/SKILL.md.
refactoring-skill
Cursor rule "refactoring-skill" from KaelSensei/MagicAIBuilder, covering refactoring skill, principles, techniques, safety and cursor behavior.
tech-lead-skill
Inspired by senior engineering practices.
cursor
.NET/ASP.NET Core Best Practices Audit - 163 practices across 18 domains with weighted scoring.
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.