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/ezbuilder/code-brain/cb-healthgit clone --depth 1 https://github.com/ezBuilder/code-brainWhat 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.00022 | $0.00351 |
| Opus 5 | $0.00011 | $0.00176 |
| Sonnet 5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
cb-health 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 2d 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
.ai/bin/ai obs health-summary --json 실행. 표·박스·이모지·헤더·해설 모두 금지. 코드 블록 사용 금지. 평문만.
JSON 경로:
okdoctor.{ok, failed[]}(failed는{name, detail}객체 배열)worker.{locked, stale, cross_host, pid, hostname}queue.{pending, processing, dead, oldest_pending_age_seconds, oldest_processing_age_seconds}index.{indexed_files, indexed_bytes}
출력 형식:
코드브레인 상태: {ok ? "정상" : "주의 필요"}
- doctor: {failed.length === 0 ? "전체 통과" : `실패 ${failed.length}건`}
{failed 배열의 각 항목마다 한 줄: " · {name}: {detail}"}
- 큐: pending {pending} / processing {processing} / dead {dead} (oldest pending {oldest_pending_age_seconds}s)
- worker: {locked ? `pid=${pid} host=${hostname}` : "미실행"}
- 인덱스: {indexed_files}파일 / {indexed_bytes}B
규칙:
- 실패 detail은 doctor 응답에 그대로 들어있다. "detail 미포함" 같은 추측 금지.
- 권장 조치/troubleshooting 안내 금지. 사용자가
/cb-doctor로 직접 확인. - 위 형식 외 한 글자도 추가하지 않는다.
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.
- 2d ago First seen · 29 lines · 22 tokens per session scan A dac1f0c99a56
cb-health is a command published in the GitHub repository ezBuilder/code-brain (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 22 tokens to every session and 351 once invoked, about $0.0001 per session on Opus 5. 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
release
Release a new version: bump version, update changelog, tag, push, and create a GitHub release.
benchmark
Run a TAU-bench evaluation end-to-end and present results.
checkout-branch
Switch to an existing branch by checking out its worktree, or creating one if needed.
kayba-agent-instructions
The kayba CLI interacts with the Kayba hosted API (https://use.kayba.ai). Auth: set KAYBAAPIKEY env var or pass --api-key to every command.
create-branch
Create a new git branch with an associated worktree following the project naming convention.
create-pr
Create a pull request for the current branch against main.