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 skills add wigtn/wigtn-plugins --skill code-review-levelsgit clone --depth 1 https://github.com/wigtn/wigtn-pluginsWrote 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/skills/wigtn/wigtn-plugins/code-review-levels)<a href="https://agentmods.dev/skills/wigtn/wigtn-plugins/code-review-levels"><img src="https://agentmods.dev/badge/skills/wigtn/wigtn-plugins/code-review-levels/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/skills/wigtn/wigtn-plugins/code-review-levels"><img src="https://agentmods.dev/badge/skills/wigtn/wigtn-plugins/code-review-levels.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.00035 | $0.00210 |
| Opus 5.5 | $0.00014 | $0.00084 |
| Sonnet 5.5 | $0.00007 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
code-review-levels 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
Code Review Levels Reference
code-reviewer 에이전트가 Level 3/4 리뷰 시 참조하는 상세 가이드입니다.
Available References
| Level | File | 용도 |
|---|---|---|
| Level 3 (Deep) | deep-review.md | 호출 체인, 에지 케이스, 동시성, 보안 심층 분석 |
| Level 4 (Architecture) | architecture-review.md | SOLID 원칙, 의존성 분석, 계층 위반 탐지, 확장성 |
Usage
code-reviewer 에이전트가 Level 3 또는 4 리뷰를 수행할 때 해당 파일을 Read하여 프로토콜을 따릅니다.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 21 lines · 35 tokens per session scan A 6a029d303063
code-review-levels is a skill published in the GitHub repository wigtn/wigtn-plugins (45 stars, last pushed 4d ago), licensed Apache-2.0. It adds 35 tokens to every session and 210 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 skills, from other repositories
apex-review
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
spine-review
API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
superreview
Review a change set or explicit project scope for intent, correctness, safety, reuse, and maintainability; independently validate findings and produce one report without applying fixes.
init
Opt-in onboarding for the mARC agent team. Scaffolds a per-repo team binding so the team graduates from ephemeral session-memory to persistent, versioned config — without ever writing a file silently. Discovers the repo's org/repo/ project at runtime via gh, prefills {{ agentsdir }}/team.toml, and (optionally) a lean…