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/briangmilnes/APAS-VERUSWrote 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/briangmilnes/apas-verus/gate-review-against-prose)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/gate-review-against-prose"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/gate-review-against-prose/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/briangmilnes/apas-verus/gate-review-against-prose"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/gate-review-against-prose.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.00311 | $0.00311 |
| Opus 5 | $0.00156 | $0.00156 |
| Sonnet 5 | $0.00062 | $0.00062 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
gate-review-against-prose 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.
What it actually says
Gate Review-Against-Prose on Changed Inputs
Before regenerating review-against-prose.md for any chapter, check whether any inputs are newer than the existing review:
find src/ChapNN/*.rs prompts/ChapNN.txt \
src/ChapNN/analyses/veracity-review-verus-proof-holes.log \
tests/test_ChapNN*.rs \
-newer src/ChapNN/analyses/review-against-prose.md 2>/dev/null | head -1
Replace ChapNN with the actual chapter (e.g., Chap56).
Decision
- Empty output → review is up to date. Skip it.
- Any output → at least one input changed. Regenerate.
Inputs that matter
| Input | Why |
|---|---|
src/ChapNN/*.rs |
Source code changed |
prompts/ChapNN.txt |
Prose text changed |
src/ChapNN/analyses/veracity-review-verus-proof-holes.log |
Proof holes changed |
tests/test_ChapNN*.rs |
Runtime tests changed |
When regenerating
Only update sections affected by the changed files. For example, if only the proof holes log changed, update the Proof Holes Summary and Action Items — don't rewrite Phase 2 (Prose Inventory).
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 · 36 lines · 311 tokens per session scan A 6e9970030f8e
gate-review-against-prose is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 311 tokens to every session, about $0.0016 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
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.