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/accept-hole-rule)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/accept-hole-rule"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/accept-hole-rule/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/accept-hole-rule"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/accept-hole-rule.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.00478 | $0.00478 |
| Opus 5 | $0.00239 | $0.00239 |
| Sonnet 5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
accept-hole-rule 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 8d 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
Accept Hole Rule
accept() is an APAS proof function (crate::vstdplus::accept::accept) that replaces
assume for intentional, reviewed holes. Adding accept() without explicit user approval
hides real proof obligations and defeats the verification effort.
Covered patterns
| Pattern | Purpose |
|---|---|
// accept hole |
Comment near external_body; Veracity treats as info |
accept(...) / proof { accept(cond); } |
APAS accept proof fn; replaces assume for intentional holes |
Rule
- DO NOT add
accept()or// accept holeproactively. EVER. - DO NOT add them to silence verification errors or proof-hole reports.
- DO NOT "fix" a failing proof by adding
accept(). That is not fixing — it is hiding. - DO add them only when the user explicitly says to (e.g., "add accept hole", "mark as accepted", "add APAS accept").
- When in doubt, leave the hole as-is and flag it for review.
Allowed assume/accept patterns (no per-instance approval needed)
These are the ONLY patterns that may exist without the user explicitly requesting each one:
assumeinsidePartialEq::eqbody (the eq/clone workaround).assumeinsideClone::clonebody (the eq/clone workaround).assume(false); diverge()in unreachable thread-join error arms.external_bodyat thread-spawn boundaries (not around algorithmic logic).
Everything else requires explicit user approval per instance.
Rationale
These annotations document known gaps. Adding them without explicit approval hides real
issues, masks incomplete verification, and makes the project's proof-hole counts meaningless.
A proof hole flagged by Veracity is data. An accept() added by an agent is lost data.
When the user asks
If the user says "add accept hole", "mark as accepted", "APAS accept", or similar, add the requested annotation at the specified location.
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.
- 8d ago First seen · 49 lines · 478 tokens per session scan A e41f5c5f38ad
accept-hole-rule is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 478 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).
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.