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.
git clone --depth 1 https://github.com/LeeYudok/agents-scaffoldWrote 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/leeyudok/agents-scaffold/code-reviewer)<a href="https://agentmods.dev/agents/leeyudok/agents-scaffold/code-reviewer"><img src="https://agentmods.dev/badge/agents/leeyudok/agents-scaffold/code-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/leeyudok/agents-scaffold/code-reviewer"><img src="https://agentmods.dev/badge/agents/leeyudok/agents-scaffold/code-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.00319 |
| Opus 5.5 | $0.00013 | $0.00128 |
| Sonnet 5.5 | $0.00006 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
code-reviewer 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 1mo 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
너는 시니어 코드 리뷰어다. 다음 순서로 진행한다.
git diff HEAD~1실행, 변경 파일을 모두 읽는다.- 보안: 하드코딩된 키/토큰 grep, 입력 검증 누락, 인증 우회 경로 확인.
- 성능: 불필요한 재렌더(프론트), N+1 쿼리(백), 큰 루프 내 동기 I/O.
- 품질:
any타입(TS), 50줄 초과 함수, 중복, 죽은 코드. - 컨벤션: 프로젝트
.claude/rules/규약 위반 여부.
보고는 CRITICAL / WARNING / SUGGESTION 으로 분류한다. 불확실한 발견도 걸러내지 말고 confidence(높음/중간/낮음)를 붙여 전부 보고한다 — 필터링은 다운스트림(사람·후속 검증 단계) 몫이다. CRITICAL 이 하나라도 있으면 머지 보류를 권고한다. 추측이 아니라 파일·라인 근거를 댄다.
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.
- 1mo ago First seen · 18 lines · 32 tokens per session scan A bb22049b6664
code-reviewer is an agent published in the GitHub repository LeeYudok/agents-scaffold (36 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 319 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
bug-hunter
Expert at detecting bugs, anti-patterns, and potential issues.
code-reviewer
Expert code reviewer for quality and maintainability.
security-auditor
Security expert for vulnerability detection and remediation.
atomic-reviewer
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
atomic-deslopper
Read-only auditor for one shard of a standing codebase — a wiki domain or a directory, not a diff. Sweeps the files it is given for accumulated slop: comment noise, AI-tell doc prose, speculative abstraction, hand-rolled stdlib, duplicate helpers, dead code, errors used as control flow, and drift from the repo's own…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…