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.
npx agentmods add rules/briangmilnes/apas-verus/module-summary-verusificationgit 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/module-summary-verusification)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/module-summary-verusification"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/module-summary-verusification.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 | $0.00531 | $0.00531 |
| Opus 5 | $0.00266 | $0.00266 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
module-summary-verusification 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.
What it actually says
Module Summary Verusification Table
When the user asks for a "module summary verusification" or "module summary" for a chapter,
produce the following table. Run veracity-review-module-fn-impls and
veracity-review-proof-holes first to get counts.
Table Format
| # | Chap | File | Trait Decl | Trait Impl | Bare Impl | Free Fn | In verus! | Outside verus! | Has Spec | Has Hole | No Spec | Iterators | PTTs |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | NN | FileName.rs | N | N | N | N | N | N | N | N | N | Yes/No | Yes/No |
Column Definitions
- Trait Decl: functions declared in a
traitblock. - Trait Impl: functions in
impl Trait for Typeblocks. - Bare Impl: functions in bare
impl Typeblocks (should be 0 per trait-impl pattern). - Free Fn: module-level free functions (clone_link, proof lemmas).
- In verus!: functions inside
verus!macro. - Outside verus!: functions outside
verus!macro (Debug, Display, macros). - Has Spec: functions with requires/ensures (strength not yet classified).
- Has Hole: functions containing
assume(),admit(), or#[verifier::external_body]. - No Spec: functions with no requires/ensures.
- Iterators: whether the module implements the collection iterator standard
(see
collection-iterators.mdc). Collection modules must have iterators. - PTTs: whether proof time tests exist for the module in
rust_verify_test/tests/.
Notes Section
After the table, add bullet notes explaining:
- What the Free Fn entries are (e.g.,
clone_linkfor Clone impl, proof lemmas). - Any accepted holes and why they exist.
- Whether iterators or PTTs are missing and needed.
When to Produce
- When the user says "module summary verusification" or "module summary".
- As part of chapter review or verusification assessment.
- 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.
- 4d ago First seen · 40 lines · 531 tokens per session scan A 0f006c4ea75e
module-summary-verusification is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 531 tokens to every session, about $0.0027 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-08-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.