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/arango-solutions/arango-sparql-py/verify-before-donegit clone --depth 1 https://github.com/arango-solutions/arango-sparql-pyWrote 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/arango-solutions/arango-sparql-py/verify-before-done)<a href="https://agentmods.dev/rules/arango-solutions/arango-sparql-py/verify-before-done"><img src="https://agentmods.dev/badge/rules/arango-solutions/arango-sparql-py/verify-before-done.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.00394 | $0.00394 |
| Opus 5 | $0.00197 | $0.00197 |
| Sonnet 5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
verify-before-done 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
Verify Before Claiming Done
"If you didn't run it, you didn't ship it."
Saying "I've implemented X" when you haven't verified X works is not a mistake — it's a lie.
Mandatory Verification
Before claiming ANY work is complete:
- Build it — compilation must succeed
- Test it — all tests must pass
- Run it — actually exercise the changed code path
- Inspect it — look at the output/behavior
For Go Code
go build ./... # Compiles?
go test ./... # Tests pass?
go test -race ./... # Race conditions?
golangci-lint run ./... # Lint issues?
For Frontend Code
npm run type-check # TypeScript compiles?
npm run lint # Lint passes?
npm run test # Tests pass?
npm run build # Production build works?
The "Done" Checklist
| Step | If No → |
|---|---|
| Did the build succeed? | Fix build errors |
| Did all tests pass? | Fix failing tests |
| Did you run the specific feature you changed? | Run it manually |
| Did you check for regressions in related areas? | Test adjacent functionality |
Anti-Patterns
- "I've updated the handler" (didn't run server) → Start server, hit endpoint, verify
- "Fixed the test" (didn't run suite) → Run
go test ./...and see green - "Added the component" (didn't view in browser) → Run dev server, navigate, verify render
Verify. Every. Time.
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 · 53 lines · 394 tokens per session scan A db233823c539
verify-before-done is a cursor rule published in the GitHub repository arango-solutions/arango-sparql-py (2 stars, last pushed 18d ago), licensed MIT. It adds 394 tokens to every session, about $0.0020 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.