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/verusification-table)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/verusification-table"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/verusification-table/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/verusification-table"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/verusification-table.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.00518 | $0.00518 |
| Opus 5.5 | $0.00207 | $0.00207 |
| Sonnet 5.5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
verusification-table 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.
What it actually says
Verusification Status Table
When the user asks for a "verusification table" or "verusification status" for a chapter, produce a structured review with the following sections.
1. Prose Coverage
Map each prose section/algorithm to implementation files. Flag missing algorithms.
| # | Prose Section | Description | File(s) | Status |
|---|---|---|---|---|
| 1 | §N Algorithm Name | Brief description | File.rs |
Implemented / Missing |
2. Per-File Verusification Status
For each source file, report structural verusification:
| # | File | verus! block | Spec fns | Trait specs | Impl bodies | Proof holes |
|---|---|---|---|---|---|---|
| 1 | File.rs |
Yes/No | count | count with ensures | verified / external_body | count × type |
3. Spec Strength Assessment
Classify every public function's spec strength and proof hole status:
| # | Function | File | Spec | Strength | Holes | Notes |
|---|---|---|---|---|---|---|
| 1 | fn_name |
File.rs | Brief spec summary | strong/partial/weak/none | verified / external_body / assume(N) / admit | Gap description |
The Holes column reports the verification status of the function body:
- verified — body fully verified, no holes
- external_body — body not checked by Verus
- assume(N) — N
assume(...)statements in body - admit — contains
admit() - A function may have multiple hole types (e.g.,
external_bodyon one arm,assumeon another)
Use the standard classification from classify-spec-strengths.mdc.
4. Summary
| Metric | Value |
|---|---|
| Strong specs | N |
| Partial specs | N |
| Weak / None specs | N |
| Fully verified bodies | N |
| external_body holes | N |
| assume holes | N |
| Prose algorithms missing | N |
When to Produce
- When the user says "verusification table", "verusification status", or "verus status"
- At the start of work on a new chapter (combined with review-against-prose)
- Before claiming a chapter is complete
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 · 55 lines · 518 tokens per session scan A ba96fe1d28d3
verusification-table is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 23d ago), licensed MIT. It adds 518 tokens to every session, about $0.0021 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).