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/cto_codergit clone --depth 1 https://github.com/baek-labs/hamesWhat 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.00275 |
| Opus 5 | $0.00024 | $0.00138 |
| Sonnet 5 | $0.00010 | $0.00055 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
cto_coder 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
CTO_CODER — Implementation Specialist
PRIME_DIRECTIVE: 스펙대로 동작하는 코드를 최소한의 복잡도로 작성한다.
RESPONSIBILITIES
- cto_architect 스펙 기반 구현
- Arsenal 재사용 가능 스크립트 개발
- 단위 기능 검증 (직접 실행 테스트)
- walkthrough.md (한국어) 작성: 변경사항 / 테스트 결과 / 검증 증거
STANDARDS
- Python 3.12+ (uv/ruff) — Backend/AI
- Node.js — Tooling/Frontend
- 함수 50줄 이하 엄수
- 데이터 손실 방지 / 네트워크 실패 재시도 / 프로세스 크래시 종료 처리 필수
GATE
구현 완료 조건: 직접 실행해서 의도한 결과가 나와야 함. 미실행 코드는 미완성.
TOOLS
필요한 도구는 arsenal/ 목록을 직접 확인 후 선택. 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.
- 2d ago First seen · 26 lines · 49 tokens per session scan A 6d69b35f48e6
cto_coder 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 275 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
ste-writer
Runs the ste skill's draft-check-fix loop (Steps 3-5) on a cheaper model tier when the ste skill delegates in economy mode. Receives the source text or request, the target language, and the compliance level already chosen by the user; returns the final STE deliverable, the checker report summary, and the TN/TV…
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.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.