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/style-review)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/style-review"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/style-review.svg" alt="Measured on agentmods" 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.00667 | $0.00667 |
| Opus 5 | $0.00333 | $0.00333 |
| Sonnet 5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
style-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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verus Style Review
Run the style review tool with:
cd ~/projects/APAS-VERUS && ~/projects/veracity/target/release/veracity-review-verus-style -c ~/projects/APAS-VERUS -e Chap21 -e vstdplus -e Types.rs -e Concurrency.rs -e experiments -e lib.rs | grep -e warning
Grep the output for warning to see only issues.
Current warnings (37 in 14 files)
[15] PartialEq/Eq/Clone should be inside verus!
- Chap06: DirGraphStEph, DirGraphMtEph, UnDirGraphStEph, UnDirGraphMtEph (PartialEq + Eq)
- Chap17: MathSeq (PartialEq + Eq)
- Chap18: ArraySeq, ArraySeqStEph, ArraySeqStPer, ArraySeqMtEph, ArraySeqMtPer, LinkedListStEph, LinkedListStPer (Clone + PartialEq + Eq)
[14] Debug/Display must be outside verus!
- Chap18/ArraySeqMtEph: Debug and Display are inside verus! — move them out
[13] Trait impls outside verus!
- Chap12/Exercise12_1: impl Default for SpinLock
- Chap12/Exercise12_5: impl Drop for ConcurrentStackMt
- Chap17/MathSeq: impl IntoIterator for MathSeqS
[17] Iterator impls
- Chap17/MathSeq: IntoIterator should be inside verus!
Excluded from review
- lib.rs (module root, no verus!), Types.rs, Concurrency.rs, Chap21, vstdplus, experiments
Pattern for moving PartialEq inside verus!
When moving impl PartialEq inside verus!, use this pattern:
use vstd::std_specs::cmp::PartialEqSpecImpl; // #[cfg(verus_keep_ghost)]
impl<T: ...> PartialEqSpecImpl for MyType<T> {
open spec fn obeys_eq_spec() -> bool { true }
open spec fn eq_spec(&self, other: &Self) -> bool { self@ == other@ }
}
impl<T: ...> Eq for MyType<T> {}
impl<T: ...> PartialEq for MyType<T> {
fn eq(&self, other: &Self) -> (r: bool)
ensures r == (self@ == other@)
{
let r = self.inner == other.inner;
proof { assume(r == (self@ == other@)); }
r
}
}
The assume is needed because Verus cannot resolve eq_spec through the trait extension machinery (attempting assert(self.eq_spec(other) == ...) crashes Verus). The trust boundary is at the leaf type (e.g., HashSetWithViewPlus::eq is external_body). Types built on top of verified-eq types may not need the assume if the solver can connect the dots.
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.
- 4d ago First seen · 64 lines · 667 tokens per session scan A 77777cd4132a
style-review is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 667 tokens to every session, about $0.0033 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
api-design
API design principles and patterns for skia-rs.
code-style
Rust code style and conventions for skia-rs.
rust-brutal-audit
Phase-based brutal audit for Rust projects - error handling, ownership, concurrency, testing.
rust-brutal-audit
Phase-based brutal audit for Rust projects - error handling, ownership, concurrency, testing.
code-quality
Cursor rule "code-quality" from tyrchen/cursor-rust-rules, covering 🦀 rust core code quality standards, 🔍 code quality strategy selection, 🎯 fundamental principles, code organization and rust edition and safety.
move-copy-semantics
Avoid std::move(const&) silent copies; use sink-by-value + std::move.