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/assume-false-diverge)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/assume-false-diverge"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/assume-false-diverge/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/assume-false-diverge"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/assume-false-diverge.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.00400 | $0.00400 |
| Opus 5 | $0.00200 | $0.00200 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
assume-false-diverge 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 6d 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
assume(false); diverge() in Thread Join
The pattern assume(false); diverge() in a JoinHandle::join() error arm
is a valid and unavoidable Verus idiom, not a proof hole to fix.
Why it exists
thread::join() returns Result<T, Box<dyn Any>> where Err means the
spawned thread panicked. Verus cannot prove that a thread will not panic —
that would require verifying the absence of all panics in the spawned
closure's entire transitive call graph, which is beyond Verus's current
scope.
The pattern
let result = match join_handle.join() {
Result::Ok(out) => out,
Result::Err(_) => { assume(false); diverge() }
};
assume(false) tells Verus "this branch is unreachable." diverge() is
a Verus built-in that satisfies any return type (it has postcondition
ensures false). Together they say: "if the thread panicked, we assume
that cannot happen."
When to use
- In any
JoinHandle::join()error arm. - In any
Result::Errarm from a thread operation that cannot fail if the spawned code is verified.
When NOT to use
- Do not use
assume(false)anywhere else without asking the user. - Do not use it to suppress verification failures in non-threading code.
Avoiding it
The ParaPair! macro encapsulates spawn/join and handles the error arms
internally, so callers never see the assume(false). Prefer ParaPair!
over raw spawn/join when the fork-join structure is symmetric.
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.
- 6d ago First seen · 50 lines · 400 tokens per session scan A cd9cd601b2c3
assume-false-diverge is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 400 tokens to every session, about $0.0020 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-module-refactor
Use when splitting Rust modules, moving tests, tightening visibility, or preserving facades during refactors.
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-native-architecture
Enforces native-first architecture and crate boundary rules for the nca workspace.