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/bedrockgit 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.00364 | $0.00364 |
| Opus 5 | $0.00182 | $0.00182 |
| Sonnet 5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
bedrock 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 3d 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
This project uses bedrock as a small project cockpit.
All project context lives in ./bedrock/.
Project cockpit
Memory/= what the project knowsWork/= what matters nowViews/= generated human inspection views
Legacy folders such as History/, Evidence/, Outputs/, or Sessions/
may still exist for compatibility. They are not the main user-facing model.
On session start
- Read
./bedrock/STATUS.md - If
onboarding: pending, readAGENTS.mdand follow First-Time Onboarding - If
onboarding: complete, read./bedrock/Memory/PROJECT.md - Read
./bedrock/Work/NOW.md - Load only the relevant Memory branches for the task
After meaningful work
- Run
/memory-updateto update the project cockpit
How Memory is split
Memory is organized per area, one doc per subsystem:
Memory/<area>.md= everything durable about that area (navigation, perception, auth, billing, ...). If work touches an area with no doc yet, create it.Memory/decisions.md= dated rationale for choices, not the design itselfMemory/PROJECT.md= cross-area overview only; it links to the area docs
Name areas after the project's own functional layers, not its hardware or file layout, so cross-cutting subsystems get a home instead of being scattered.
When the context window is getting long
- Run
/compact-contextto save the project cockpit and reset context
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.
- 3d ago First seen · 44 lines · 364 tokens per session scan A d9fe3a351286
bedrock is a cursor rule published in the GitHub repository robotaitai/project-bedrock (44 stars, last pushed 13d ago), licensed MIT. It adds 364 tokens to every session, about $0.0018 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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.