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/savagelysubtle/big-brain-memory-bank/verification-checklistgit clone --depth 1 https://github.com/savagelysubtle/BIG-BRAIN-Memory-BankWrote 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/savagelysubtle/big-brain-memory-bank/verification-checklist)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/verification-checklist"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/verification-checklist.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.1 | $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 6d 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.
This is a copy
100% identical to verification-checklist — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 6d ago First seen · 159 lines · 1,182 tokens per session scan A 00cae22a3b19
verification-checklist is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 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. It is 100% identical to verification-checklist, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
composer-coding-excellence
Coding craft — surgical edits, convention matching, no scope creep, no slop comments, no fabricated APIs.
composer-core
Always-on builder spine — continue the app, demoable slice, Build loop, Run/Wired handoff, ask only on high confusion weight.
composer-reasoning
High-stakes judgment for architectural or multi-option work — tradeoffs, one-way doors, reason-then-re-evaluate, honest pushback.
clarify-first
Infer-and-act by default — ask only on high confusion weight, after inspecting, with a decision-linked question.
composer-debugging
Root-cause debugging — reproduce, trace data flow, test cheapest hypothesis, fix the cause not the symptom.
composer-deep-research
Edge-case research for audits, vendor comparisons, and unfamiliar APIs — primaries first, iterative retrieval, explicit conflicts; not the default build path.