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/robotaitai/project-bedrock/memory-bootstrapgit clone --depth 1 https://github.com/robotaitai/project-bedrockWhat 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 | $0.00513 | $0.00513 |
| Opus 5 | $0.00257 | $0.00257 |
| Sonnet 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 2d 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.
- 2d 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 (44 stars, last pushed 12d ago), licensed MIT. It adds 513 tokens to every session, about $0.0026 per session on Opus 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.