Borrowing it
Nothing to install: this file belongs to opensesh/karimo-overview. 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/opensesh/karimo-overview/main/.claude/commands/bos-sync-karimo.mdgit clone --depth 1 https://github.com/opensesh/karimo-overviewWrote 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/opensesh/karimo-overview/bos-sync-karimo)<a href="https://agentmods.dev/commands/opensesh/karimo-overview/bos-sync-karimo"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/bos-sync-karimo/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/opensesh/karimo-overview/bos-sync-karimo"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/bos-sync-karimo.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.00742 |
| Opus 5.5 | $0.00000 | $0.00297 |
| Sonnet 5.5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
bos-sync-karimo 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bos-sync-karimo - Sync KARIMO Artifacts
Sync KARIMO learnings and PRD artifacts to the BOS context and memory systems.
Usage
/bos-sync-karimo [--all] [--learnings] [--prds]
Arguments
| Argument | Description |
|---|---|
--all |
Sync both learnings and PRDs (default) |
--learnings |
Sync only KARIMO learnings to memories |
--prds |
Sync only PRD documents to context |
What Gets Synced
Learnings → Memories
KARIMO learnings are synced to BOS memories with the following category mapping:
| KARIMO Category | BOS Category |
|---|---|
patterns |
patterns |
anti-patterns |
cases |
project-notes |
preferences |
execution-rules |
patterns |
PRDs → Context Embeddings
PRD documents are embedded as L1 context entries:
PRD_*.md→bos://karimo/prd/{slug}findings.md→bos://karimo/prd/{slug}/findings
Behavior
- Parse the sync target from arguments
- For learnings:
- Read all category index files from
.karimo/learnings/ - Check for duplicates in memory system (0.9 similarity threshold)
- Add new learnings with
source: 'karimo'
- Read all category index files from
- For PRDs:
- Scan all PRD directories in
.karimo/prds/ - Compare content hashes to detect changes
- Embed and store new/updated PRDs
- Scan all PRD directories in
Implementation
Execute this command to sync:
# Sync all
bunx tsx .bos/scripts/sync-karimo.ts --all
# Sync only learnings
bunx tsx .bos/scripts/sync-karimo.ts --learnings
# Sync only PRDs
bunx tsx .bos/scripts/sync-karimo.ts --prds
Example Output
🔄 BOS KARIMO Sync
📖 Syncing KARIMO learnings...
✅ New pattern added
Learnings:
Total: 19
Added: 1
Updated: 0
Skipped: 18
📄 Syncing KARIMO PRDs...
✅ Added: 005_new-feature
🔄 Updated: 001_brand-color-studio
PRDs:
Total: 5
Added: 1
Updated: 1
Skipped: 3
✅ Sync complete
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 · 120 lines · 0 tokens per session scan A 0189066c77fc
bos-sync-karimo is a command published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 742 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
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
run
Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.
merge
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.