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/MeenakshiSundaram-MS/prove-itWrote 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/meenakshisundaram-ms/prove-it/prove-it-strict)<a href="https://agentmods.dev/rules/meenakshisundaram-ms/prove-it/prove-it-strict"><img src="https://agentmods.dev/badge/rules/meenakshisundaram-ms/prove-it/prove-it-strict/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/meenakshisundaram-ms/prove-it/prove-it-strict"><img src="https://agentmods.dev/badge/rules/meenakshisundaram-ms/prove-it/prove-it-strict.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.00034 | $0.00950 |
| Opus 5.5 | $0.00014 | $0.00380 |
| Sonnet 5.5 | $0.00007 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
prove-it-strict 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prove-it — Strict Mode
Four gates. All must show PASS ✓. None are optional.
Use for: production features, security-sensitive code, public APIs, database migrations, anything with direct user-visible behavior.
Gate 1 — Compile / Type Check
Show the build is clean before running any tests.
GATE 1 — COMPILE
─────────────────
Command: [tsc --noEmit | cargo build | go build ./... | mvn compile -q | go vet ./...]
Output: [paste output — empty output means clean]
Status: PASS ✓
Language-specific Gate 1 commands:
- TypeScript:
npx tsc --noEmit - Go:
go build ./... && go vet ./... - Rust:
cargo build(cargo test includes this — run separately for clarity) - Java/Maven:
mvn compile -q - Java/Gradle:
./gradlew compileJava
Gate 2 — Regression (existing test suite)
The full existing test suite must pass. Zero regressions from this change.
GATE 2 — REGRESSION
────────────────────
Command: [full test suite command]
Output: [paste output — show total pass count]
Status: PASS ✓ (N tests, 0 failures)
Pre-existing failures
If the suite was already failing before your change, you must document it:
Pre-existing failure: [test name]
Cause: [known issue / unrelated to this change]
Evidence: [this test was failing on main before this branch]
Do NOT claim Gate 2 passes if pre-existing failures exist without documentation. Do NOT hide pre-existing failures by skipping them.
Gate 3 — New Tests
New behavior requires new tests. Show them passing.
GATE 3 — NEW TESTS
───────────────────
Tests added: [list test names or file path]
Command: [run new tests — filter to new tests if possible, else full suite]
Output: [paste passing output]
Status: PASS ✓ (M new tests)
If you cannot add tests (read-only test dir, external dependency with no test interface): document why and describe what manual verification covers it.
Gate 4 — Edge Cases
For every function added or modified, identify and handle:
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 · 136 lines · 34 tokens per session scan A 830295ab2dbb
prove-it-strict is a cursor rule published in the GitHub repository MeenakshiSundaram-MS/prove-it (2 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 950 once invoked, about $0.0001 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
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.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
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.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.