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/CSOAI-ORG/councilof-aiWrote 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/csoai-org/councilof-ai/csoai-review)<a href="https://agentmods.dev/rules/csoai-org/councilof-ai/csoai-review"><img src="https://agentmods.dev/badge/rules/csoai-org/councilof-ai/csoai-review/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/csoai-org/councilof-ai/csoai-review"><img src="https://agentmods.dev/badge/rules/csoai-org/councilof-ai/csoai-review.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.00517 | $0.00517 |
| Opus 5 | $0.00259 | $0.00259 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
csoai-review 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 11d 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
CSOAI review rules — flag these, they are real recurring defects
The estate's one rule: a component must be structurally unable to report success on a path it did not complete. Not "log the error" — unable. In review, flag any of the following as a bug, not a nit:
-
Two outcomes where there must be three. Any grader/scorer that maps an unparsed / empty / failed result to
0or "wrong" instead of UNMEASURED. Unparsed must leave the denominator, never score as incorrect. (This shipped four times in one day.) -
A guard that can pass on an empty scan. A contamination / validation check that reads zero rows and returns "clean" is a false pass. An empty scan must be fatal, not silent.
-
An interval below the gate. Any confidence interval / ranking published below
usable_n >= 30, including ours. Small-n must withhold the interval explicitly. -
A claim without its test. A capability asserted in a name, comment, or string with no code that enforces it. If a function is called
verify_*/refuse_*/check_*, the body must actually do it. -
Sign AND significance. A "beats"/"improves" verdict that checks only whether a CI excludes zero, not whether the delta is positive in sign. (An earlier verdict printed "beats" for a −9.16 delta.)
-
Contamination by row instead of by theme. Held-out splits must be theme-level: if any item in a statutory theme is in training, the whole theme leaves the clean split.
-
Secrets in code or logs. No tokens/keys inline; secrets come via keystone. Flag any printed secret.
-
Silent truncation / caps. Any top-N, sampling, or no-retry bound that is not logged. Silent truncation reads as "covered everything" when it didn't.
When unsure whether something is a defect: if the code could report success on a path it didn't complete, it is one.
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.
- 11d ago First seen · 38 lines · 517 tokens per session scan A 1a82a83f44d6
csoai-review is a cursor rule published in the GitHub repository CSOAI-ORG/councilof-ai (0 stars, last pushed today), licensed MIT. It adds 517 tokens to every session, about $0.0026 per session on Opus 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-31.
Other cursor rules, from other repositories
env-validation-gate
Env validation gate — every app with ≥1 required env var validates its contract at boot via Zod; raw process.env is banned outside the env module. Full pattern in .claude/skills/t2000-env-gate/.
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.
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.