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/table-of-contents-standard)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/table-of-contents-standard"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/table-of-contents-standard/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/table-of-contents-standard"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/table-of-contents-standard.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.00795 | $0.00795 |
| Opus 5 | $0.00398 | $0.00398 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
table-of-contents-standard 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 12d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Table of Contents Standard
Every Verus source file should follow this section ordering. Place a TOC comment near the top of the file (after the copyright and module doc), and use section headers to mark each section that is present.
TOC format
// Table of Contents
// 1. module
// 2. imports
// 3. broadcast use
// 4. type definitions
// 5. view impls
// 6. spec fns
// 7. proof fns/broadcast groups
// 8. traits
// 9. impls
// 10. iterators
// 11. derive impls in verus!
// 12. macros
// 13. derive impls outside verus!
Section headers
Mark each section with a numbered comment:
// 8. traits
Section contents
| # | Section | What goes here |
|---|---|---|
| 1 | module | pub mod ModName { |
| 2 | imports | use statements, #[cfg(verus_keep_ghost)] use |
| 3 | broadcast use | broadcast use groups |
| 4 | type definitions | struct, enum, type aliases |
| 5 | view impls | impl View for ... |
| 6 | spec fns | spec fn, open spec fn, closed spec fn |
| 7 | proof fns/broadcast groups | proof fn, broadcast group |
| 8 | traits | Trait definitions (trait Foo { ... }) |
| 9 | impls | impl blocks for the main type (exec functions) |
| 10 | iterators | Custom iter struct, View, iter_invariant, Iterator::next, ghost iter, ForLoopGhostIteratorNew, ForLoopGhostIterator, IntoIterator, iter() method |
| 11 | derive impls in verus! | Clone, PartialEq, Eq, Default, Drop — inside verus! with specs |
| 12 | macros | macro_rules! — outside verus! |
| 13 | derive impls outside verus! | Debug, Display, iter_mut, IntoIterator for &mut — outside verus! |
Tooling
Use veracity-review-verus-style to reorder a file and insert the TOC automatically:
veracity-review-verus-style -r -c ~/projects/APAS-VERUS -d src/ChapNN/File.rs
Flags:
-r/--reorder— reorder items insideverus!{}to match the standard and insert the TOC-c— project root (paths are relative to this)-d— the file to process-n— dry-run: preview changes without writing to disk
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.
- 12d ago First seen · 84 lines · 795 tokens per session scan A 0555b3598c8b
table-of-contents-standard is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 795 tokens to every session, about $0.0040 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
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.