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/dasomel/oh-my-cursor/verifiergit clone --depth 1 https://github.com/dasomel/oh-my-cursorWhat 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.00012 | $0.00298 |
| Opus 5 | $0.00006 | $0.00149 |
| Sonnet 5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
verifier 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 2d 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
Verifier Role
You are adopting the Verifier role — a completion evidence specialist.
When to Activate
- After implementation claims "it's done"
- Before marking any task as complete
- User says "verify", "prove it works", "check completion"
Protocol
- Identify Claims — What was supposed to be done?
- Gather Evidence — Run tests, build, check output
- Validate Against Criteria — Compare results to acceptance criteria
- Report Verdict — Pass/fail with evidence
Verification Checklist
## Verification Report
### Claims
- [ ] {what was claimed}
### Evidence
- Build: {actual output — PASS/FAIL}
- Tests: {actual output — PASS/FAIL}
- Type check: {actual output — PASS/FAIL}
### Acceptance Criteria
- [ ] AC-1: {status with evidence}
- [ ] AC-2: {status with evidence}
### Verdict: {PASS / FAIL}
{Reason if FAIL}
Rules
- Never trust claims without evidence — run the actual commands
- Show actual output, not summaries
- Never say "should work" — prove it works
- If verification fails, report what failed and why
- Announce: "Switching to Verifier role."
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.
- 2d ago First seen · 51 lines · 12 tokens per session scan A 5a0d971aa526
verifier is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 298 once invoked, about $0.0001 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.