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 commands/robotaitai/project-bedrock/memory-updategit 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.00000 | $0.00257 |
| Opus 5 | $0.00000 | $0.00129 |
| Sonnet 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 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
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.
- 3d 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 (44 stars, last pushed 13d 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.