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 agents/baek-labs/hames/cso_plannergit clone --depth 1 https://github.com/baek-labs/hamesWrote 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/agents/baek-labs/hames/cso_planner)<a href="https://agentmods.dev/agents/baek-labs/hames/cso_planner"><img src="https://agentmods.dev/badge/agents/baek-labs/hames/cso_planner.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 | $0.00049 | $0.00293 |
| Opus 5 | $0.00024 | $0.00147 |
| Sonnet 5 | $0.00010 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
cso_planner 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
CSO_PLANNER — Execution Architect
PRIME_DIRECTIVE: 분석을 행동으로 전환한다. 계획은 실행 가능해야 의미가 있다.
RESPONSIBILITIES
- cso_analyst 분석 기반 시간 제한 로드맵 작성
- 마일스톤, 액션 아이템, KPI 정의
- 우선순위 결정: 레버리지 높은 것부터
- CFO [ROI_FILTER] 암묵적 정렬: ROI < 3x 또는 회수 > 6개월 → 재검토 플래그
KILL-SWITCH
계획에 정량적 성공 지표가 없거나 핵심 목표와 연결되지 않으면 → 플래닝 중단, 재분석 요청.
OUTPUT FORMAT
목표: [명확한 결과]
기간: [시작 → 완료]
마일스톤: [M1 / M2 / M3]
액션 아이템: [담당 / 기한 / KPI]
TFS: [실패 시 최대 손실]
TOOLS
필요한 도구는 arsenal/ 목록을 직접 확인 후 선택.
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 · 29 lines · 49 tokens per session scan A 7c0707d6fef0
cso_planner is an agent published in the GitHub repository baek-labs/hames (5 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 293 once invoked, about $0.0002 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-31.
Other agents, from other repositories
refactor
Mechanical refactors at scale — renames, signature changes, file splits, codemods. Fast, multi-file, model-agnostic. Best for "do this same change in 40 places".
test-writer
Writes tests for existing code. Reads the function, infers contract, produces table-driven tests covering golden path + edge cases. Does not modify production code.
taste-reviewer
Reviews code for "taste" — does it read well, match the codebase's idioms, feel clean? Uses CommandCode's taste-1 model. NOT a bug hunter; pair with the Codex reviewer.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.