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 skills/ezbuilder/code-brain/lean-reviewnpx skills add ezBuilder/code-brain --skill lean-reviewgit 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.00344 |
| Opus 5 | $0.00011 | $0.00172 |
| Sonnet 5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
lean-review 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
현재 diff나 지정 범위를 correctness/security가 아니라 과설계 관점으로만 검토한다.
찾을 항목:
delete: 죽은 코드, 투기적 기능, 사용되지 않는 유연성stdlib: 표준 라이브러리로 대체 가능한 직접 구현native: 플랫폼/DB/CSS/브라우저 기본 기능으로 대체 가능한 코드나 의존성yagni: 구현체 하나뿐인 abstraction/factory/wrapper, 설정값 하나뿐인 configshrink: 같은 동작을 더 짧게 표현할 수 있는 코드
보고 형식:
<file>:L<line>: <delete|stdlib|native|yagni|shrink>: <cut>. <replacement>.
끝에 net: -<N> lines possible.을 적는다. 줄일 것이 없으면 Lean already. Ship.만 적는다.
범위:
- 수정하지 않고 보고만 한다.
- correctness, security, performance 이슈는 일반
code-review로 넘긴다. - 최소 smoke/self-check는 과설계로 보지 않는다.
KEEP(과설계로 보지 않는다 — 삭제 후보로 올리지 말 것):
- 경계 입력 검증, I/O·외부호출 예외 처리, 데이터 손실/유실 방지 코드
- 비자명한 이유를 설명하는 WHY 주석
- 접근성·보안·검증 로직, 명시적 요구사항
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 · 33 lines · 22 tokens per session scan A b1fe56b63cd7
lean-review is a skill 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 344 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 skills, from other repositories
kayba-stage-3-metrics
Define metrics from Kayba insights, implement them as Python measurement code, run against traces, and iterate until the metrics are clean and meaningful. Trigger when the user says "run stage 3", "define metrics", "build metrics", "compute baselines", or when invoked by the kayba-pipeline orchestrator. Requires…
kayba-stage-4-rubric
Organize computed metrics into a tiered evaluation rubric with leading, lagging, and quality indicators. Trigger when the user says "run stage 4", "build rubric", "tier metrics", or when invoked by the kayba-pipeline orchestrator. Requires eval/baselinemetrics.json and eval/computebaselines.py to exist.
kayba-stage-5-action-plan
Triage each insight into discard/code-fix/prompt-fix and produce a prioritized action plan with specific recommendations. Trigger when the user says "run stage 5", "make action plan", "triage skills", or when invoked by the kayba-pipeline orchestrator. Requires eval outputs from stages 1-4.
kayba-stage-6-hitl
Human-In-The-Loop gate that presents the action plan with full context, collects an informed approval/modification/rejection decision, and records the outcome. Trigger when the user says "run stage 6", "HITL review", "approve action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md…
kayba-stage-2-domain-context
Gather domain context about the repository and agent — system prompt, tool definitions, domain docs, and behavior patterns from traces. Trigger when the user says "run stage 2", "gather context", "domain context", or when invoked by the kayba-pipeline orchestrator.
kayba-stage-7-fixer
Implement the approved fixes from the action plan and log all changes. Trigger when the user says "run stage 7", "implement fixes", "apply action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md to exist.