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/chapter-standalone)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/chapter-standalone"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/chapter-standalone/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/chapter-standalone"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/chapter-standalone.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.00315 | $0.00315 |
| Opus 5.5 | $0.00126 | $0.00126 |
| Sonnet 5.5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
chapter-standalone 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
Implementation Files Stand Alone
Different implementations of the same algorithm (StEph, StPer, MtEph) must not import specs or lemmas from each other, unless the APAS textbook explicitly specifies that one builds on another.
Rule
XStEph.rs, XMtEph.rs, and XStPer.rs are sibling implementations of algorithm X. Each must be self-contained. A student reading one file should not need to open another to understand the specs and proofs.
Scope
- In scope:
BSTPlainStEphmust not import fromBSTPlainMtEphorBSTPlainStPer;MergeSortMtPermust not import fromMergeSortStPer; etc. - Out of scope:
BSTAVLimporting fromBSTPlainwhen APAS presents AVL as extending plain BST — that is a different algorithm building on another, not a variant implementation.
What to do
- Define spec functions and proof lemmas locally in each implementation file.
- Duplicate shared specs across StEph/MtEph/StPer when needed.
Exception
When APAS explicitly presents one algorithm as building on another (e.g., AVL extends plain BST), follow the textbook and document the dependency.
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 · 28 lines · 315 tokens per session scan A 44abd83ab305
chapter-standalone is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 23d ago), licensed MIT. It adds 315 tokens to every session, about $0.0013 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).