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/proof-holes)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/proof-holes"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/proof-holes/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/proof-holes"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/proof-holes.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.00364 | $0.00364 |
| Opus 5 | $0.00182 | $0.00182 |
| Sonnet 5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
proof-holes 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 5d 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
Check for Proof Holes
ALWAYS use veracity-review-proof-holes for any proof hole related query. Do NOT use grep or manual searching.
~/projects/veracity/target/release/veracity-review-proof-holes -d src/
Or for a specific directory:
~/projects/veracity/target/release/veracity-review-proof-holes -d src/Chap05/
What It Detects
| Hole Type | Description |
|---|---|
assume(false) |
Assumes a contradiction (proves anything) |
assume(...) |
Assumes arbitrary conditions without proof |
admit() |
Explicitly admits without proof |
#[verifier::external_body] |
Body not verified |
#[verifier::external_fn_specification] |
External function spec |
#[verifier::external] |
Fully external |
STOP: Ask Before Adding Proof Holes
NEVER add #[verifier::external_body], admit(), or assume(...) without first asking the user for permission. These introduce unverified assumptions and must be explicitly approved.
When to Run
- When asked to report/show/list/find proof holes (any such query)
- After completing a proof function
- Before committing proof work
- When claiming a module is "proven"
Understanding Results
- Clean: No unverified assumptions - the proof is complete
- Holed: Contains at least one proof hole - more work needed
A proof is not truly complete until it reports as clean.
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.
- 5d ago First seen · 49 lines · 364 tokens per session scan A c21e1a6ff20a
proof-holes is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 364 tokens to every session, about $0.0018 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-09-03.
Other cursor rules, from other repositories
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.