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/commands/robotaitai/project-bedrock/knowledge-sync)<a href="https://agentmods.dev/commands/robotaitai/project-bedrock/knowledge-sync"><img src="https://agentmods.dev/badge/commands/robotaitai/project-bedrock/knowledge-sync/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/knowledge-sync"><img src="https://agentmods.dev/badge/commands/robotaitai/project-bedrock/knowledge-sync.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.00205 |
| Opus 5.5 | $0.00000 | $0.00082 |
| Sonnet 5.5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
knowledge-sync 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
Knowledge Sync
Knowledge sync is the connected-project maintenance flow for the adaptive memory system. It writes through ./agent-knowledge, which should resolve to the external project knowledge folder.
Behavior
- inspect current repo changes
- classify touched files into the relevant
agent-knowledge/Memory/branch notes - append durable recent-change entries when knowledge meaningfully changed
- optionally record a decision note when explicitly requested
- refresh raw and imported evidence without treating it as curated truth
- update
agent-knowledge/STATUS.md
Safety
- use
--dry-runto preview all file writes - idempotent reruns should not duplicate recent-change bullets
- sessions and evidence stay separate from durable memory
Expected Script Entry Point
scripts/update-knowledge.sh --project /path/to/project
scripts/update-knowledge.sh --project /path/to/project --decision-title "Adopt X"
scripts/update-knowledge.sh --project /path/to/project --dry-run
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 · 27 lines · 0 tokens per session scan A c660872c5200
knowledge-sync is a command published in the GitHub repository robotaitai/project-bedrock (45 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 205 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.