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.
npx agentmods add rules/briangmilnes/apas-verus/chapter-proof-targetinggit 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-proof-targeting)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/chapter-proof-targeting"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/chapter-proof-targeting.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 | $0.00009 | $0.00416 |
| Opus 5 | $0.00005 | $0.00208 |
| Sonnet 5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
chapter-proof-targeting 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 4d 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
Chapter Proof Targeting — Read Before Planning
When planning proof work, agent assignments, or round plans, always read Section 4.6 of the global proof holes log first:
analyses/veracity-review-verus-proof-holes.log → Section 4.6. Chapter by Chapter Proof Targeting
This section contains:
- Clean chapters — zero holes, no work needed.
- Holed chapters — hole count, file count, whether deps are clean (
ClnDeps?), and which external holed modules block them. - Dependency chain — chapter-level blockers (external only).
How to use it
- Read Section 4.6 before making any work plan. Search for
4.6. Chapter by Chapter Proof Targetingin the log. - Prioritize clean-deps chapters (
ClnDeps? = YES) — these can be closed without waiting on other chapters. - Identify the critical path from the dependency chain. Currently Chap37 is the root blocker for the longest chain (37 → 41 → 42 → 43 → 52).
- Partition work by file to avoid agent overlap. The section lists which modules block which chapters — use this to assign non-overlapping file sets.
- Internal-only deps (
ClnDeps? = internal) can be closed by fixing files within the same chapter.
When to regenerate
Run scripts/all-holes-by-chap.sh to regenerate the log (includes Section 4.6) after:
- Merging agent branches
- Any proof work that changes hole counts
- Structural changes (renames, new files)
Do NOT run per-chapter scripts/holes.sh when you need the global picture — it overwrites
per-chapter logs without producing the global analysis.
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.
- 4d ago First seen · 43 lines · 9 tokens per session scan A e0bc3fd06847
chapter-proof-targeting is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 416 once invoked, about $0.0000 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.