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/robotaitai/project-bedrockWrote 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/robotaitai/project-bedrock/memory-bootstrap)<a href="https://agentmods.dev/rules/robotaitai/project-bedrock/memory-bootstrap"><img src="https://agentmods.dev/badge/rules/robotaitai/project-bedrock/memory-bootstrap/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/robotaitai/project-bedrock/memory-bootstrap"><img src="https://agentmods.dev/badge/rules/robotaitai/project-bedrock/memory-bootstrap.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.00513 | $0.00513 |
| Opus 5.5 | $0.00205 | $0.00205 |
| Sonnet 5.5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
memory-bootstrap 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Bootstrap
Check for a valid memory tree at the start of any session that involves real project work. If missing, overly generic, or obviously stale, bootstrap it first.
Check condition
Look for agent-knowledge/Memory/MEMORY.md in the project root.
The local ./agent-knowledge path is the project entrypoint and should point to the real dedicated knowledge folder.
| State | Action |
|---|---|
| File exists and has real content (not just template placeholders) | Skip -- proceed with the task |
| File exists but contains only bootstrap placeholders or generic text | Re-bootstrap or backfill: read project-ontology-bootstrap skill |
File is missing, empty, or the agent-knowledge pointer is broken |
Bootstrap: read project-ontology-bootstrap skill |
"Real content" means the memory root has frontmatter and at least one branch note contains verified facts in Current State.
Bootstrap steps (summary -- full detail in skill)
- Read the
project-ontology-bootstrapskill. - Ensure the local
./agent-knowledgepointer exists and resolves to the external knowledge folder. If it does not, runscripts/install-project-links.shfirst. - Run
scripts/bootstrap-memory-tree.sh .to create the minimal scaffold. - Inspect repo structure, manifests, docs, configs, tests, and workflows.
- Infer the project ontology and create 2-4 initial branch notes using the project's own terminology.
- Use the same-name branch convention:
<topic>.mdfor flat notes,<topic>/<topic>.mdfor branches with subtopics. - Collect evidence with
scripts/import-agent-history.sh . - If the project already has history, apply
history-backfill. - Confirm the tree is in place before proceeding with the user's task.
When to skip
- Memory tree exists with real content -- always skip, do not re-bootstrap
- User explicitly asked to skip bootstrap -- skip for this session only
- The task is purely read-only exploration -- bootstrap is optional (do it anyway if convenient)
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.
- 1mo ago First seen · 54 lines · 513 tokens per session scan A 155713dc6613
memory-bootstrap is a cursor rule published in the GitHub repository robotaitai/project-bedrock (45 stars, last pushed 1mo ago), licensed MIT. It adds 513 tokens to every session, about $0.0021 per session on Opus 5.5. 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-30.
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…
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.
memsprout
Cursor rule "memsprout" from memsprout/agents, covering using memsprout, search first, capturing, spaces and topics and files.