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/170-protocol-enforcement-mechanisms)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/170-protocol-enforcement-mechanisms"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/170-protocol-enforcement-mechanisms/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/savagelysubtle/big-brain-memory-bank/170-protocol-enforcement-mechanisms"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/170-protocol-enforcement-mechanisms.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.03754 |
| Opus 5 | $0.00000 | $0.01877 |
| Sonnet 5 | $0.00000 | $0.00751 |
| Haiku 4.5 | $0.00000 | $0.00375 |
Grade A, and why
170-protocol-enforcement-mechanisms 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 10d 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 — 616 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: WHEN executing commands ENFORCE protocol compliance for memory bank operations globs: ["/*.md", "/*.mdc"] alwaysApply: true
TL;DR: The Protocol Enforcement Mechanisms ensure adherence to command protocols, workflow processes, and memory maintenance requirements through systematic validation, enforcement, and correction mechanisms.
1.0.0
1. **Command Protocols**
- Command structure correctness
- Parameter validity
- Option compatibility
- Command sequence appropriateness
- Command context alignment
2. **Workflow Protocols**
- Workflow phase sequence
- Phase entry/exit conditions
- Required artifacts
- Decision documentation
- Validation checkpoints
3. **Memory Maintenance Protocols**
- Required file updates
- Consistency requirements
- Reference integrity
- Documentation standards
- Version control practices
4. **Verification Protocols**
- Required verification steps
- Validation criteria
- Quality standards
- Review requirements
- Approval processes
Each protocol type has specific enforcement mechanisms.
1. **Validation Gates**
- Pre-execution validation of protocol requirements
- Verification of prerequisites and conditions
- Confirmation of required context
- Approval for critical operations
2. **Process Guardrails**
- Runtime checks during execution
- Boundary enforcement for operations
- Progress verification at milestones
- State integrity protection
3. **Correction Guidance**
- Specific direction for protocol violations
- Remediation suggestions
- Alternative approaches
- Learning resources
4. **Compliance Documentation**
- Record of protocol adherence
- Deviation documentation
- Exception handling
- Enforcement actions
These mechanisms ensure protocols are maintained throughout operations.
1. **Structure Validation**
- Syntax checking against command schema
- Parameter type validation
- Option compatibility verification
- Required parameter confirmation
2. **Context Validation**
- Workflow state compatibility
- Prerequisite command verification
- Resource availability confirmation
- Command appropriateness for task
3. **Execution Control**
- Permission verification
- Resource allocation checking
- Impact assessment
- Risk-based execution controls
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.
- 10d ago First seen · 616 lines · 0 tokens per session scan A 39ee7056eb36
170-protocol-enforcement-mechanisms 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,754 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".
web
Web build conventions (separate from native and RN JS).
components
Component patterns and UI conventions.
git
Git workflow and commit conventions.
verification-before-completion
Require fresh, scope-appropriate evidence before any completion claim. Distinguishes implemented, locally verified, repository-green, PR-green, deployed, and observed-stable states.
_project
Project-wide conventions and developer environment context (RN monorepo, no-Mac dev).