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/kfnzero/mantis-mcp-server/verification-checklistgit clone --depth 1 https://github.com/kfnzero/mantis-mcp-serverWhat 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.01182 | $0.01182 |
| Opus 5 | $0.00591 | $0.00591 |
| Sonnet 5 | $0.00236 | $0.00236 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
verification-checklist 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- verification-checklist — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VERIFICATION CHECKLIST (SIMPLIFIED)
TL;DR: Before completing any task, run through this verification checklist. A task is only complete when all checks pass. This version uses tasks.md as the single source of truth for task status.
⚠️ VERIFICATION COMMITMENT
Add this at the start of every task:
## Verification Commitment
I WILL run the full verification checklist before completing this task.
I will maintain tasks.md as the single source of truth for task status.
📋 QUICK VERIFICATION STEPS
Before finishing any task, verify these essentials:
- File Types: Critical files have correct type (file vs. directory)
- Platform: Commands adapted for current operating system
- Workflow: All 6 sections completed in correct order
- Tasks: All task statuses updated in tasks.md
- Commands: All commands executed one at a time
- Documentation: Implementation details added to activeContext.md
- Archive: Task properly archived with all sections
- Links: Cross-references properly set up
🚨 TOP 5 MOST COMMON FAILURES
- .cursorrules as directory: Created .cursorrules as a directory instead of a file
- Incorrect task tracking: Updated task status in multiple files or wrong file
- Command chaining: Used && or similar to chain commands
- Insufficient implementation details: Failed to add details to activeContext.md
- Missing creative phases: Failed to use creative phases for major architectural/design decisions
1️⃣ FILE TYPE VERIFICATION
✓ FILE TYPE VERIFICATION
- .cursorrules is a FILE (not directory)? [YES/NO]
- memory-bank is a DIRECTORY? [YES/NO]
- docs/archive is a DIRECTORY? [YES/NO]
2️⃣ PLATFORM VERIFICATION
✓ PLATFORM VERIFICATION
- Operating system correctly identified? [YES/NO]
- Commands adapted for platform? [YES/NO]
- Platform information documented in techContext.md? [YES/NO]
3️⃣ WORKFLOW VERIFICATION
✓ WORKFLOW VERIFICATION
- All 6 section headers used in correct order? [YES/NO]
- Each section was completed before moving to next? [YES/NO]
- Section tracking list updated after each section? [YES/NO]
- Section transition markers used? [YES/NO]
- Creative phases used for all major design decisions (Level 3-4)? [YES/NO/NA]
- Creative phase verification completed for each phase? [YES/NO/NA]
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 · 159 lines · 1,182 tokens per session scan A 00cae22a3b19
verification-checklist is a cursor rule published in the GitHub repository kfnzero/mantis-mcp-server (10 stars, last pushed 1y ago), licensed MIT. It adds 1,182 tokens to every session, about $0.0059 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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.