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-locations)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/verus-locations"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/verus-locations/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-locations"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/verus-locations.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.00192 | $0.00192 |
| Opus 5 | $0.00096 | $0.00096 |
| Sonnet 5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
verus-locations 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 Source Locations
vstd (Verified Standard Library)
~/projects/verus/source/vstd/
This contains the verified standard library including:
seq.rs,set.rs,map.rs- Core collection specsseq_lib.rs- Sequence lemmashash_set.rs,hash_map.rs- Hash collection wrappersstd_specs/- Specs for Rust std library
Verus Test Code
~/projects/verus/source/rust_verify_test/tests/
This contains Verus's own test suite including:
loops.rs- Loop verification patternshash.rs- HashSet/HashMap tests- Pattern examples for many Verus features
Use these as reference when figuring out how to verify something.
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 · 33 lines · 192 tokens per session scan A d4ea7333c96b
verus-locations is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 192 tokens to every session, about $0.0010 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
core
Core STT/TTS abstraction layer documentation.
rust-architect
PoolAI — Rust Architect workflow: runtime stack, MSYS2, target/ disk, pre-push checks, docs sync.
rust-development-standards
Rust development standards: idioms, style, anti-patterns (Rust 2021 edition, 2024 where applicable).
ivolgaql-project
General development rules for ИволгаQL, an early-stage Rust project with a command-line and TCP server interface. They define the project structure, Russian user experience, coding conventions, testing, builds, and commit-message format.
rust-hexagonal
Règles Rust Architecture Hexagonale avec gRPC (tonic).
secure-dev-rust
These rules apply to all Rust code in the repository and aim to prevent common security risks through disciplined use of memory safety, input validation, error handling, and safe APIs.