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/validate)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/validate"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/validate/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/validate"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/validate.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.00752 | $0.00752 |
| Opus 5.5 | $0.00301 | $0.00301 |
| Sonnet 5.5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
validate 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation Modes
Always use the shell scripts. Do not type raw verus commands.
validate (default) — full verification
When the user says "validate", run:
scripts/validate.sh
dev_only_validate — foundation modules only
When the user says "dev_only_validate" or "dov", run with the dev_only feature. This skips all chapters and verifies only foundation (Types, Concurrency, vstdplus):
scripts/validate.sh dev_only
To include specific chapters in dev_only mode, edit src/lib.rs and change their cfg from:
#[cfg(not(any(feature = "experiments_only", feature = "dev_only")))]
to:
#[cfg(not(feature = "experiments_only"))]
Remember to include transitive dependencies (see dependency table in lib.rs comments).
V1 — validate once
When the user says "V1", run a single Verus verification. If working with experiments_only:
scripts/validate.sh exp
Otherwise, same as validate. Do not iterate or fix errors. Just run once, show the full output, and stop.
Proof Holes
Use the wrapper scripts for hole queries (never call the binary directly):
scripts/holes.sh src/ChapNN/ # single chapter or file
scripts/all-holes-by-chap.sh # all chapters, writes to analyses/ logs
Run scripts/all-holes-by-chap.sh after any rename or structural change that affects
proof hole analysis output. The per-chapter logs live at
src/ChapNN/analyses/veracity-review-verus-proof-holes.log.
Analysis Scripts
All analysis scripts write per-chapter output to src/ChapNN/analyses/. Run them after
renames, structural changes, or when refreshing analysis baselines.
| Script | Output per chapter |
|---|---|
scripts/all-holes-by-chap.sh |
veracity-review-verus-proof-holes.log |
scripts/all-style-by-chap.sh |
veracity-review-verus-style.log |
scripts/all-fn-impls-by-chap.sh |
veracity-review-module-fn-impls.{md,json} |
Running Suites
Run validate, rtt, and ptt sequentially, not in parallel. They compete for CPU and memory, making all three slower than running them one at a time.
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 · 98 lines · 752 tokens per session scan A 4ae9a16cb283
validate is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 23d ago), licensed MIT. It adds 752 tokens to every session, about $0.0030 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-31.
Other cursor rules, from other repositories
tensorflow
TensorFlow: Keras, model training, production deployment.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.