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/partialeq-eq-pattern)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/partialeq-eq-pattern"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/partialeq-eq-pattern/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/partialeq-eq-pattern"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/partialeq-eq-pattern.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.00574 | $0.00574 |
| Opus 5.5 | $0.00230 | $0.00230 |
| Sonnet 5.5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
partialeq-eq-pattern 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PartialEq / Eq Specification Pattern
All PartialEq and Eq implementations MUST be inside verus! {} with specifications. Do NOT use #[verifier::external_body] on equality — use assume inside the proof body instead.
Required Components
Every type that implements equality needs three pieces, all inside verus! {}:
1. PartialEqSpecImpl (ghost spec, cfg-gated)
#[cfg(verus_keep_ghost)]
impl<T: View + PartialEq> PartialEqSpecImpl for MyType<T> {
open spec fn obeys_eq_spec() -> bool { true }
open spec fn eq_spec(&self, other: &Self) -> bool { self@ == other@ }
}
2. Eq marker (empty impl)
impl<T: Eq + View> Eq for MyType<T> {}
3. PartialEq with ensures and assume
impl<T: PartialEq + View> 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
}
}
Why assume and not external_body
external_bodyhides the entire function body from Verus — no verification at all.assumeonly introduces one specific trusted assertion while the rest of the body is still verified.- The
assumeis needed because Verus cannot resolveeq_specthrough the trait extension machinery. - The trust boundary is small and explicit: we trust that the underlying
==on the inner type correctly reflects view equality.
Do NOT
- Do NOT place
PartialEqorEqimpls outsideverus! {}— they will have no specification and callers cannot reason about equality results. - Do NOT use
#[verifier::external_body]onfn eq— useassumeinside the body. - Do NOT omit
PartialEqSpecImpl— it connects the Verus spec world to the execPartialEq. - Do NOT omit the
ensuresclause — it is the contract callers rely on.
Import
The PartialEqSpecImpl trait requires:
#[cfg(verus_keep_ghost)]
use vstd::std_specs::cmp::PartialEqSpecImpl;
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 · 67 lines · 574 tokens per session scan A e08f14a93572
partialeq-eq-pattern is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 23d ago), licensed MIT. It adds 574 tokens to every session, about $0.0023 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
rust-module-refactor
Use when splitting Rust modules, moving tests, tightening visibility, or preserving facades during refactors.
rust-architect
PoolAI — Rust Architect workflow: runtime stack, MSYS2, target/ disk, pre-push checks, docs sync.
core
Core STT/TTS abstraction layer documentation.
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.
ivolgaql-parser-language
Project rules for building ИволгаQL, a query language and server that uses Russian commands and messages. They cover how new language features move through the lexer, parser, engine, and network protocol.
rust-development-standards
Rust development standards: idioms, style, anti-patterns (Rust 2021 edition, 2024 where applicable).