Borrowing it
Nothing to install: this file belongs to robotaitai/project-bedrock. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/robotaitai/project-bedrock/main/.claude/commands/memory-update.mdgit 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/commands/robotaitai/project-bedrock/memory-update)<a href="https://agentmods.dev/commands/robotaitai/project-bedrock/memory-update"><img src="https://agentmods.dev/badge/commands/robotaitai/project-bedrock/memory-update/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/commands/robotaitai/project-bedrock/memory-update"><img src="https://agentmods.dev/badge/commands/robotaitai/project-bedrock/memory-update.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.00257 |
| Opus 5.5 | $0.00000 | $0.00103 |
| Sonnet 5.5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
memory-update 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.
What it actually says
Update the project cockpit.
Steps:
- Run in terminal:
bedrock sync --project . - Review what changed and what was learned
- Update
./bedrock/Memory/with stable, confirmed project knowledge -- put area-specific facts in that area's own doc (Memory/<area>.md), creating it if the area has none yet - Update
./bedrock/Work/NOW.mdif the current focus, next actions, or blockers changed - Update
./bedrock/Work/open-questions.md,./bedrock/Work/risks.md, or./bedrock/Work/backlog.mdif needed - Summarize what changed in Memory, what changed in Work, and what was intentionally skipped
Rules:
- Stable facts go into
Memory/, in the doc for the area they belong to - One doc per subsystem:
Memory/<area>.mdfor the design,Memory/decisions.mdfor dated rationale,Memory/PROJECT.mdfor the cross-area overview only - Current priorities and open loops go into
Work/ - Generated site or graph output stays in
Views/ - Do not dump raw session notes into the cockpit
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 · 17 lines · 0 tokens per session scan A 4efe3b2c22f5
memory-update is a command published in the GitHub repository robotaitai/project-bedrock (45 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 257 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-30.
Other commands, from other repositories
lavra-checkpoint
Save session progress by filing beads, capturing knowledge, and syncing state.
context-age
Envejecimiento semántico del decision-log — comprime y archiva decisiones antiguas.
handoff
Write a session handoff document for continuity.
org-succession
Succession planning with real readiness — not paper. Per critical role: identified successor, readiness gap, 6-12-month development plan, tested partial in-role, named timeline, transparent communication. Refuses paper-only succession plans. Surfaces single-points-of-failure, unprepared successors, and undisclosed…
perf-review-redesign
Replace a broken annual performance ritual with a research-backed continuous + quarterly + annual-comp architecture. Produces redesigned cadence, manager scripts, employee-prep guide, calibration protocol, and a transition plan from old to new. Heavy disclaimer on legal/HRIS implications because changing comp linkage…
talent-burnout-detect
Run a burnout detection protocol on a person or team. Maslach 3-dimensional assessment (emotional exhaustion + cynicism + reduced personal accomplishment) plus root-cause hypothesis plus intervention plan plus reassessment cadence. Cynicism is the diagnostic. Hard clinical-boundary escalation when signals cross into…