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/in-out-table)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/in-out-table"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/in-out-table.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.1 | $0.00476 | $0.00476 |
| Opus 5 | $0.00238 | $0.00238 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
in-out-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 7d 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
In/Out Table
When the user says "in-out table" or "in/out table", audit what code is inside vs outside verus! blocks and produce the table below.
Format
| # | Chapter | File | Clone | PartialEq/Eq | Default | Drop | Iterator | Debug | Display | Macro | Other |
|---|
Column Values
✅ in= correctly insideverus!✅ out= correctly outsideverus!(required — Verus limitation)❌ in= incorrectly inside (should be outside)❌ out= incorrectly outside (should be inside)-= not implemented
What Goes Inside verus!
These trait impls CAN and SHOULD be inside verus! with specifications:
- Clone — with
ensures cloned@ == self@if possible - PartialEq / Eq — per
partialeq-eq-pattern.mdc(PartialEqSpecImpl + ensures + assume) - Default — delegates to
new(), noexternal_bodyneeded - Drop — requires
#[verifier::external_body],opens_invariants none,no_unwind - Iterator infrastructure — custom iter struct, View, iter_invariant, Iterator::next, ghost iter struct, ForLoopGhostIteratorNew, ForLoopGhostIterator, IntoIterator for &Self, IntoIterator for Self, iter() method
What Must Stay Outside verus!
- Debug / Display — Verus does not support fmt traits
macro_rules!— macros are expanded before verification- Unsafe marker traits —
Sync,Send &mut-returning methods —iter_mut(),IntoIterator for &mut Self#[cfg(...)]stubs — compatibility code for non-Verus builds
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.
- 7d ago First seen · 43 lines · 476 tokens per session scan A 356d48874e74
in-out-table is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 476 tokens to every session, about $0.0024 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-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.
rust-development-standards
Rust development standards: idioms, style, anti-patterns (Rust 2021 edition, 2024 where applicable).
cube-engine
Use when changing Rust puzzle state, moves, notation, scrambles, or validation.
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.