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/opensesh/karimo-overview/bos-refreshgit 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-refresh)<a href="https://agentmods.dev/commands/opensesh/karimo-overview/bos-refresh"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/bos-refresh.svg" alt="Measured on agentmods" 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.00512 |
| Opus 5 | $0.00000 | $0.00256 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
bos-refresh 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 6d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bos-refresh - Regenerate BOS Context Cache
Regenerate the L0/L1 context summaries in .bos/context/.
Usage
/bos-refresh [--all] [--section <name>]
Arguments
| Argument | Description |
|---|---|
--all |
Regenerate all sections (default) |
--section <name> |
Regenerate specific section: architecture, components, lib |
Behavior
-
Run the context generator script:
bunx tsx .bos/scripts/generate-context.ts -
Report what was regenerated:
- Number of L1 sections updated
- Total files analyzed
- Git commit hash
-
Show cache freshness from
manifest.json
Output Files
The command regenerates:
.bos/context/
├── index.md # L0: Project overview (~500 tokens)
├── architecture/
│ ├── index.md # L1: Architecture overview
│ ├── app-router.md # L1: Next.js routing patterns
│ └── data-flow.md # L1: Data flow patterns
├── components/
│ ├── index.md # L1: Component library overview
│ ├── ui.md # L1: Design system primitives
│ └── chat.md # L1: Chat components
├── lib/
│ ├── index.md # L1: Core libraries overview
│ ├── ai.md # L1: AI provider system
│ └── supabase.md # L1: Database services
└── manifest.json # Cache metadata
When to Use
Run /bos-refresh when:
- Starting a new feature that touches multiple areas
- After significant codebase changes
- When context feels stale or inaccurate
- Periodically during development sessions
Implementation
# Run the generator
bunx tsx .bos/scripts/generate-context.ts
# Check freshness
cat .bos/context/manifest.json | jq '.generatedAt, .gitCommit'
Related
.claude/reference/context-layers.md- L0/L1/L2 model explanation.bos/scripts/generate-context.ts- Generator implementation/bos-search- Search context with vector similarity (Phase B2)
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.
- 6d ago First seen · 79 lines · 0 tokens per session scan A ca0e35729a12
bos-refresh is a command published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 512 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
项目上下文管理：初始化 .context 目录、记录决策日志、压缩归档、查看历史.
cozempic
Diagnose and prune bloated Claude Code context. Run to slim down the current session before compacting or resuming.
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
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.
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.
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.