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/moclam1905/CocktailRecipesWrote 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/moclam1905/cocktailrecipes/van-file-verification)<a href="https://agentmods.dev/rules/moclam1905/cocktailrecipes/van-file-verification"><img src="https://agentmods.dev/badge/rules/moclam1905/cocktailrecipes/van-file-verification.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.00000 | $0.00441 |
| Opus 5 | $0.00000 | $0.00220 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
van-file-verification 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 7d 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
VAN MODE: FILE VERIFICATION
TL;DR: Checks for the existence and basic structure of essential Memory Bank and documentation components.
📁 FILE VERIFICATION PROCESS
graph TD
FV["File Verification"] --> CheckFiles["Check Essential Files"]
CheckFiles --> CheckMB["Check Memory Bank<br>Structure"]
CheckMB --> MBExists{"Memory Bank<br>Exists?"}
MBExists -->|"Yes"| VerifyMB["Verify Memory Bank<br>Contents (Basic)"]
MBExists -->|"No"| CreateMB["Create Memory Bank<br>Structure (Basic)"]
CheckFiles --> CheckDocs["Check Documentation<br>Files (e.g., tasks.md)"]
CheckDocs --> DocsExist{"Docs<br>Exist?"}
DocsExist -->|"Yes"| VerifyDocs["Verify Documentation<br>Presence"]
DocsExist -->|"No"| CreateDocs["Create Essential<br>Documentation Files"]
VerifyMB & CreateMB --> MBCP["Memory Bank<br>Checkpoint"]
VerifyDocs & CreateDocs --> DocsCP["Documentation<br>Checkpoint"]
MBCP & DocsCP --> FileComplete["File Verification<br>Complete"]
style FV fill:#4da6ff,stroke:#0066cc,color:white
style FileComplete fill:#10b981,stroke:#059669,color:white
style MBCP fill:#f6546a,stroke:#c30052,color:white
style DocsCP fill:#f6546a,stroke:#c30052,color:white
📋 CHECKPOINT VERIFICATION TEMPLATE (Example)
✓ SECTION CHECKPOINT: FILE VERIFICATION
- Memory Bank Directory Exists/Created? [YES/NO]
- Essential Docs (tasks.md) Exist/Created? [YES/NO]
→ If all YES: File Verification Complete.
→ If any NO: Resolve before proceeding.
Next Step: Load and process van-complexity-determination.mdc.
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.
- 7d ago First seen · 49 lines · 0 tokens per session scan A 3844a69b4688
van-file-verification is a cursor rule published in the GitHub repository moclam1905/CocktailRecipes (1 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 441 tokens. 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
workflow-memory
Workflow memory operating loop — read root state before acting, write state back after meaningful change.
ai-context-management
Rule Name: ai-context-management Description: When the conversation context is getting long or the model is losing track of details, proactively summarize and restructure context.
documentation
Documentation: code docs, READMEs, ADRs, maintenance.
document
A set of project rules for writing and maintaining documentation, including README files and changelogs. A README explains a project to users, while a changelog records its changes over time.
00-workflow
Before responding to any request, call getsessioncontext.
resume
Resume from last checkpoint with state drift detection — validate persisted assumptions before continuing.