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/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/130-validation-reporting-system)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/130-validation-reporting-system"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/130-validation-reporting-system.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.03669 |
| Opus 5 | $0.00000 | $0.01835 |
| Sonnet 5 | $0.00000 | $0.00734 |
| Haiku 4.5 | $0.00000 | $0.00367 |
Grade A, and why
130-validation-reporting-system 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.
How it starts
The opening of the file, as written. The whole thing — 575 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: WHEN verification completes GENERATE comprehensive reports on memory bank health globs: ["/*.md", "/*.mdc"] alwaysApply: true
TL;DR: The Validation Reporting System generates comprehensive reports on Memory Bank health, displaying verification results, identifying issues, and providing actionable insights for maintaining optimal operation.
1.0.0
1. **Initialization Report**
- Comprehensive verification at session start
- Full Memory Bank health assessment
- Critical issues highlighted
- Ready-state confirmation
2. **Operation Report**
- Focused verification during active sessions
- Task-relevant components verified
- Context-specific validation
- Operational impact assessment
3. **Bedtime Report**
- Comprehensive pre-shutdown verification
- Memory persistence validation
- Update confirmation
- Readiness for next session
4. **Recovery Report**
- Post-recovery verification results
- Resolution effectiveness assessment
- Remaining issues identification
- Prevention recommendations
Each report type has specialized formats and content emphasis.
```
## 🛡️ Memory Bank Validation Report
### Summary
- Report type: [Initialization/Operation/Bedtime/Recovery]
- Timestamp: [YYYY-MM-DD HH:MM:SS]
- Overall status: [Optimal/Healthy/Attention Required/Critical]
- Health score: [0-100%]
- Files verified: [Count]
- Issues found: [Count by severity]
### Verification Results
- File Verification: [Pass/Partial/Fail] - [Score]
- Consistency Checks: [Pass/Partial/Fail] - [Score]
- Reference Validation: [Pass/Partial/Fail] - [Score]
- Structural Integrity: [Pass/Partial/Fail] - [Score]
### Issues
#### Critical Issues
- [Issue description]
> Location: [File:Section]
> Impact: [Description of operational impact]
> Resolution: [Recommended action]
#### Warnings
- [Warning description]
> Location: [File:Section]
> Impact: [Description of potential impact]
> Resolution: [Recommended action]
#### Notices
- [Notice description]
> Location: [File:Section]
> Recommendation: [Improvement suggestion]
### Health Metrics
- Completeness: [Percentage]
- Consistency: [Percentage]
- Timeliness: [Percentage]
- Accessibility: [Percentage]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional recommendation]
### Verification History
- Previous status: [Status from last report]
- Trend: [Improving/Stable/Declining]
- Recent changes: [Significant changes since last report]
```
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 · 575 lines · 0 tokens per session scan A 7147c7c523e4
130-validation-reporting-system is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,669 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
wrapup
End-of-session wrap-up: summarizes the session and pushes a log to the project's linked NotebookLM notebook. Activate with @wrapup in chat, or "wrap up", "save this session", or "end of session".
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…
search-routing
Smart Search Routing — always use QMD semantic search when available, never bypass with grep for vault content.
composer-coding-excellence
Coding craft — surgical edits, convention matching, no scope creep, no slop comments, no fabricated APIs.
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.