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.
npx agentmods add rules/savagelysubtle/big-brain-memory-bank/801-bedtime-protocolgit 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/801-bedtime-protocol)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/801-bedtime-protocol"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/801-bedtime-protocol.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.00774 |
| Opus 5 | $0.00000 | $0.00387 |
| Sonnet 5 | $0.00000 | $0.00155 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
801-bedtime-protocol 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.
What it actually says
description: WHEN user mentions "Bedtime Protocol" THEN immediately follow the step-by-step process in the README.md file globs: */
<phase name="Memory Preservation & Organization">
<step>Update memory config file for archiving original files</step>
<step>Execute memory manager dry run to preview operations</step>
<step>Verify and execute file operations</step>
<step>Perform final verification that everything is correctly preserved</step>
</phase>
<critical-note>
The detailed steps in the README.md file are the authoritative source and must be followed exactly. This summary is only for general awareness.
</critical-note>
This protocol is critical for preserving memory between sessions and must be followed precisely. Failure to follow the exact procedure may result in permanent memory loss.
<bad-practice>
<description>Incorrect Bedtime Protocol response</description>
<example>
"I'll help you implement the Bedtime Protocol by moving some files around.
Let me start by copying these files to the archive folder..."
[Not consulting the README file for precise instructions]
</example>
</bad-practice>
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 · 82 lines · 0 tokens per session scan A 39f404478189
801-bedtime-protocol 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 774 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.
cursor
This project uses Gnosys for persistent memory via MCP. Gnosys uses a centralized brain (/.gnosys/gnosys.db) shared across all projects with project, user, and global scopes.