Archon: Command for Claude Code

.claude/commands/validation/code-review.md

code-review is a command for Claude Code from coleam00/Archon. It costs 13 tokens per session (781 once invoked), scanned A, original, MIT.

A technical code-review command for checking recent changes against project rules and common software risks. Code review means examining code for defects, security problems, performance issues, and maintainability concerns.

In plain words
What is it for?
Use it to inspect changed or newly added files for logic errors, missing error handling, security issues, performance problems, and compliance with project documentation.
Why use it?
It provides a structured check before changes are committed, helping catch problems that may not appear during normal implementation.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is coleam00/Archon's own configuration. It tells Claude Code how to work on Archon itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Archon configures →

About the project

Archon is a workflow engine for AI coding agents that turns development processes into YAML-defined sequences with phases, validation gates, and artifacts. Developers use it to run repeatable processes such as planning, implementation, testing, code review, and pull-request creation across projects. The catalogue entries provide commands, agents, skills, hooks, instructions, and settings for working with Archon.

coleam00/Archon · 23,752 stars · on GitHub · archon.diy

Reuse

Borrowing it

Nothing to install: this file belongs to coleam00/Archon. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/coleam00/Archon/dev/.claude/commands/validation/code-review.md
Clone the repo
git clone --depth 1 https://github.com/coleam00/Archon

Made for: Claude Code.

Wrote 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.

agentmods badge for code-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/coleam00/archon/code-review/github.svg)](https://agentmods.dev/commands/coleam00/archon/code-review)
Your own site
<a href="https://agentmods.dev/commands/coleam00/archon/code-review"><img src="https://agentmods.dev/badge/commands/coleam00/archon/code-review/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.

agentmods 80×15 button for code-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/coleam00/archon/code-review"><img src="https://agentmods.dev/badge/commands/coleam00/archon/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 781 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.00781
Opus 5.5 $0.00005 $0.00312
Sonnet 5.5 $0.00003 $0.00156
Haiku 4.5 $0.00001 $0.00078

Measured 9d ago against content hash 949e7bd4f18e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-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 9d 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.

.claude/commands/validation/code-review.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Review: Pre-Commit Quality Check

Objective

Perform a thorough technical code review on recently changed files, checking for bugs, security issues, and adherence to Archon's documented conventions.

Process

1. Gather Codebase Context

Read the project conventions to understand what standards to enforce:

  • Read AGENTS.md for project-wide conventions
  • Read any relevant .claude/rules/ files for domain-specific patterns

2. Identify Changes to Review

git status
git diff HEAD
git diff --stat HEAD

Check for new untracked files:

git ls-files --others --exclude-standard

Read each new file in its entirety. Read each changed file in its entirety (not just the diff) to understand full context.

3. Review Checklist

For each changed or new file, analyze for:

Logic Errors

  • Off-by-one errors, incorrect conditionals
  • Missing error handling or silent failures
  • Race conditions (especially in async/streaming code)
  • Incorrect TypeScript type narrowing

Security Issues

  • SQL injection in raw queries
  • XSS in rendered content
  • Exposed secrets or API keys
  • Insecure data handling

Performance Problems

  • N+1 database queries
  • Missing cleanup (event listeners, intervals, AbortControllers)
  • Unnecessary re-renders in React components
  • Unbounded array growth

Type Safety

  • Use of any without justification
  • Missing type annotations on functions
  • Incorrect type assertions (as casts)
  • Overly broad types where narrow types exist

Archon-Specific Conventions

  • Import patterns: import type for type-only imports, no import * as core
  • Use execFileAsync not exec for git operations
  • Never git clean -fd
  • Structured Pino logging with {domain}.{action}_{state} event naming
  • bun run test not bun test from repo root
  • mock.module() isolation (separate test batches for conflicting mocks)
  • Lint passes with zero warnings (bun run lint)

Package Boundary Compliance

  • No circular dependencies between packages
  • @archon/git and @archon/paths must not import from @archon/core
  • @archon/workflows injects deps via narrow interfaces, not direct core imports

Read the full file on GitHub · 114 lines

Changes

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.

  1. 9d ago Changed 949e7bd4f18e
  2. 17d ago Changed · -1 tokens per session f3a7eda39397
  3. 1mo ago First seen · 114 lines · 14 tokens per session scan A dd1b5ea3c6b8

Subscribe to this mod's changes

code-review is a command published in the GitHub repository coleam00/Archon (23,752 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 781 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.