van-file-verification

van-file-verification is a cursor rule for Cursor from Angry-Robot-Deals/ace-mcp. It costs 0 tokens per session (2,337 once invoked), scanned A, a copy of van-file-verification, MIT.

A file-verification process map for VAN mode that checks whether required memory-bank files and other file structures are complete before implementation. It uses grouped checks and defined pass-or-abort decisions.

In plain words
What is it for?
Use it when verifying files in VAN mode, especially to check the memory bank, run pattern-based batch checks, and confirm critical structure before implementation.
Why use it?
It helps catch missing or incomplete project records before work begins. The process stops when required checks fail, so file-structure problems can be fixed first.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when verifying files in VAN mode, especially to check the memory bank, run pattern-based batch checks, and confirm critical structure before implementation.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/angry-robot-deals/ace-mcp/van-file-verification
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Angry-Robot-Deals/ace-mcp

Made for: Cursor.

Wrote 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.

agentmods badge for van-file-verification

README.md
[![agentmods](https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/van-file-verification/github.svg)](https://agentmods.dev/rules/angry-robot-deals/ace-mcp/van-file-verification)
Your own site
<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/van-file-verification"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/van-file-verification/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for van-file-verification

Your own site · 80×15
<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/van-file-verification"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/van-file-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,337 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02337
Opus 5 $0.00000 $0.01169
Sonnet 5 $0.00000 $0.00467
Haiku 4.5 $0.00000 $0.00234

Measured 9d ago against content hash 3e36b9b7741b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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.

Origin

This is a copy

100% identical to van-file-verification — 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.

.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-file-verification.mdc · 302 lines

How it starts

The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OPTIMIZED FILE VERIFICATION SYSTEM

🚨 CRITICAL: MEMORY BANK VERIFICATION REQUIRED 🚨 Memory Bank structure MUST exist before any file operations This check MUST be executed first in all verification processes

TL;DR: This system provides a structured approach to verify file structure integrity before task implementation, with emphasis on efficient checks and clear status reporting.

🔍 FILE VERIFICATION WORKFLOW

graph TD
    %% Critical Memory Bank verification - MUST be first
    Start["Start File Verification"] --> MemBankCheck{"Memory Bank<br>Exists?"}
    MemBankCheck -->|"No"| CreateMemBank["CREATE MEMORY BANK<br>[CRITICAL]"]
    MemBankCheck -->|"Yes"| VerifyMemBankComplete["Verify Memory Bank<br>Structure Complete"]
    CreateMemBank --> VerifyMemBankComplete
    
    VerifyMemBankComplete --> PassCheck{"All Critical<br>Checks Pass?"}
    PassCheck -->|"No"| AbortAll["⛔ ABORT ALL OPERATIONS<br>Fix Memory Bank First"]
    PassCheck -->|"Yes"| MainVerification

    %% Regular verification flow continues here
    MainVerification["Start Full<br>File Verification"] --> BatchVerify["Batch Verification<br>Using Patterns"]
    BatchVerify --> BrokenLinks["Check for<br>Broken References"]
    BrokenLinks --> DirectoryStructure["Verify Directory<br>Structure"]
    DirectoryStructure --> Status{"All Verifications<br>Successful?"}
    
    Status -->|"Yes"| Complete["Verification<br>Complete ✓"]
    Status -->|"No"| Diagnose["Diagnose<br>Issues"]
    Diagnose --> Attempt{"Attempt Auto<br>Resolution?"}
    
    Attempt -->|"Yes"| AutoFix["Auto-Fix<br>Issues"]
    Attempt -->|"No"| ReportIssue["Report Issues to<br>User"]
    
    AutoFix --> Recheck{"Issues<br>Resolved?"}
    Recheck -->|"Yes"| ReportSuccess["Report Success<br>to User"]
    Recheck -->|"No"| ReportIssue
    
    ReportSuccess --> Complete
    ReportIssue --> UserAction["Wait for<br>User Action"]
    UserAction --> ReVerify["Re-Verify<br>After User Action"]
    ReVerify --> Status
    
    style MemBankCheck fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
    style CreateMemBank fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
    style VerifyMemBankComplete fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
    style PassCheck fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
    style AbortAll fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
    style Status fill:#f6546a,stroke:#c30052,color:white
    style Complete fill:#10b981,stroke:#059669,color:white

Read the full file on GitHub · 302 lines

Changes

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.

  1. 9d ago First seen · 302 lines · 0 tokens per session scan A 3e36b9b7741b

Subscribe to this mod's changes

van-file-verification is a cursor rule published in the GitHub repository Angry-Robot-Deals/ace-mcp (4 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,337 tokens. A static security scan graded it A with 0 findings. It is 100% identical to van-file-verification, differing in 0 lines, and is treated as a copy.