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/Angry-Robot-Deals/ace-mcpWrote 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/angry-robot-deals/ace-mcp/file-verification)<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/file-verification"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/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.
<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/file-verification"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/file-verification.svg" alt="Reviewed on agentmods" width="80" 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.01382 |
| Opus 5 | $0.00000 | $0.00691 |
| Sonnet 5 | $0.00000 | $0.00276 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
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.
This is a copy
100% identical to 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.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPTIMIZED FILE VERIFICATION SYSTEM
TL;DR: This system efficiently verifies and creates required Memory Bank file structures using batch operations and platform-optimized commands.
🔍 OPTIMIZED FILE VERIFICATION WORKFLOW
graph TD
Start["Start File<br>Verification"] --> VerifyAll["Verify All<br>Required Components"]
VerifyAll --> MissingCheck{"Missing<br>Components?"}
MissingCheck -->|"Yes"| BatchCreate["Batch Create<br>All Missing Items"]
MissingCheck -->|"No"| Complete["Verification<br>Complete"]
BatchCreate --> Report["Generate<br>Verification Report"]
Report --> Complete
📋 OPTIMIZED DIRECTORY CREATION
graph TD
Start["Directory<br>Creation"] --> DetectOS["Detect Operating<br>System"]
DetectOS -->|"Windows"| WinCmd["Batch Create<br>Windows Command"]
DetectOS -->|"Mac/Linux"| UnixCmd["Batch Create<br>Unix Command"]
WinCmd & UnixCmd --> Verify["Verify<br>Creation Success"]
Verify --> Complete["Directory Setup<br>Complete"]
Platform-Specific Commands
Windows (PowerShell)
# Create all directories in one command
mkdir memory-bank, docs, docs\archive -ErrorAction SilentlyContinue
# Create all required files
$files = @(".cursorrules", "tasks.md",
"memory-bank\projectbrief.md",
"memory-bank\productContext.md",
"memory-bank\systemPatterns.md",
"memory-bank\techContext.md",
"memory-bank\activeContext.md",
"memory-bank\progress.md")
foreach ($file in $files) {
if (-not (Test-Path $file)) {
New-Item -Path $file -ItemType File -Force
}
}
Mac/Linux (Bash)
# Create all directories in one command
mkdir -p memory-bank docs/archive
# Create all required files
touch .cursorrules tasks.md \
memory-bank/projectbrief.md \
memory-bank/productContext.md \
memory-bank/systemPatterns.md \
memory-bank/techContext.md \
memory-bank/activeContext.md \
memory-bank/progress.md
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.
- 9d ago First seen · 198 lines · 0 tokens per session scan A b615b17a68df
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 1,382 tokens. A static security scan graded it A with 0 findings. It is 100% identical to file-verification, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
context-recorder-system
A modular system for recording project context, decisions, requirements, and lessons in structured files. It divides the recorder into core, template, advanced, and edge-case modules.
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.