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/verus-tests)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/verus-tests"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/verus-tests/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/verus-tests"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/verus-tests.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.00057 | $0.00057 |
| Opus 5 | $0.00028 | $0.00028 |
| Sonnet 5 | $0.00011 | $0.00011 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
verus-tests 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 5d 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
Verus Tests
Verus proof tests are located at:
~/projects/verus/source/rust_verify_test/tests/
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.
- 5d ago First seen · 14 lines · 57 tokens per session scan A 7f2159574c10
verus-tests is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session, about $0.0003 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-09-03.
Other cursor rules, from other repositories
researchforge-validate
Run repeated validation benchmarks on a run's finalists so a result can honestly be called validated. Use after a run has a promising winner, or when the user asks to confirm/validate a result.
openproblems-submission
Prepare a spatial transcriptomics method for contribution to an OpenProblems benchmark (e.g. taskistpreprocessing). Use when the user wants to submit/contribute a method, open a PR to a task repo, or check submission readiness.
sweep-accuracy
Audit xrspatial modules for numerical accuracy issues: floating point precision, NaN propagation, off-by-one errors, Earth curvature corrections, backend inconsistencies, reference divergence.
sweep-reference-validation
Validate xrspatial algorithms against reference implementations (gdaldem, scipy.ndimage, richdem, WhiteboxTools) on shared synthetic inputs; divergence becomes an accuracy fix, parity becomes a golden-value regression test.
validate
Validate a function's numerical accuracy against reference implementations and across all four backends.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.