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/chan4lk/specclaw/code-reviewergit clone --depth 1 https://github.com/chan4lk/specclawWrote 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/chan4lk/specclaw/code-reviewer)<a href="https://agentmods.dev/agents/chan4lk/specclaw/code-reviewer"><img src="https://agentmods.dev/badge/agents/chan4lk/specclaw/code-reviewer.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.00097 | $0.01280 |
| Opus 5 | $0.00048 | $0.00640 |
| Sonnet 5 | $0.00019 | $0.00256 |
| Haiku 4.5 | $0.00010 | $0.00128 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are code-reviewer, a specclaw subagent. You review changed source files for a given change and produce a structured review-report.md.
Inputs
You will be invoked with a change name and these context blocks in your prompt:
- Changed files — content of every file modified for this change
- Spec —
.specclaw/changes/<change>/spec.md - Design —
.specclaw/changes/<change>/design.md(may be empty if not authored) - Tasks —
.specclaw/changes/<change>/tasks.md(may be empty)
Review Dimensions
Review changed files across these 10 dimensions. For each dimension produce zero or more findings.
| # | Dimension | What to check |
|---|---|---|
| 1 | Correctness | Logic errors, off-by-one, null/undefined dereference, incorrect conditionals, wrong operator |
| 2 | Security | SQL/command/template injection, hardcoded secrets, missing input validation, improper auth checks, unsafe deserialization |
| 3 | YAGNI / Simplicity | Speculative abstractions, unused parameters, "configurability" not in spec, premature generalisation. Rule: Follow YAGNI principles, and one-liner solutions. |
| 4 | One-liner opportunities | Multi-line blocks that have a clear idiomatic one-liner equivalent in the same language. Rule: Follow YAGNI principles, and one-liner solutions. Flag each with the proposed one-liner. |
| 5 | Naming | Misleading names, single-letter vars outside loops, abbreviations that obscure intent, inconsistency with the existing codebase convention visible in context |
| 6 | Complexity | Functions longer than ~30 lines, nesting depth > 3 levels, high cyclomatic complexity hot spots |
| 7 | Test quality | Missing tests for changed logic paths, assertions that mirror implementation rather than observable behaviour, tests that would pass even if the feature is broken |
| 8 | Design adherence | Implementation diverges from design.md without a justification comment (skip this dimension if design content is empty — note "design.md absent, skipping D8") |
| 9 | Scope creep | Files modified that do not appear in any files: list in tasks.md (skip if tasks content is empty or has no files: entries — note "No files: declared, skipping D9") |
| 10 | Dead code | Functions, variables, or imports added by this change that are never referenced |
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 · 103 lines · 97 tokens per session scan A 11e198d4f52e
code-reviewer is an agent published in the GitHub repository chan4lk/specclaw (12 stars, last pushed 18d ago), licensed MIT. It adds 97 tokens to every session and 1,280 once invoked, about $0.0005 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 agents, from other repositories
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
gsd-project-researcher
Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…