review-simplify

review-simplify is a command for coding agents from coleam00/Archon. It costs 0 tokens per session (1,210 once invoked), scanned A, original, MIT.

A read-only code-review command looks for unnecessary structure: parts of a change that make it harder to maintain without protecting required behavior.

In plain words
What is it for?
Use it to examine a change against its intended outcome, design rules, tests, data contracts, security boundaries, and shared-state risks.
Why use it?
It helps identify complexity that adds maintenance work or makes future changes harder without a clear benefit.

Command

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,374 stars · on GitHub

Install

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.

agentmods
npx agentmods add commands/coleam00/archon/review-simplify
Clone the repo
git clone --depth 1 https://github.com/coleam00/Archon

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 review-simplify

README.md
[![agentmods](https://agentmods.dev/badge/commands/coleam00/archon/review-simplify.svg)](https://agentmods.dev/commands/coleam00/archon/review-simplify)
Your own site
<a href="https://agentmods.dev/commands/coleam00/archon/review-simplify"><img src="https://agentmods.dev/badge/commands/coleam00/archon/review-simplify.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,210 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01210
Opus 5 $0.00000 $0.00605
Sonnet 5 $0.00000 $0.00242
Haiku 4.5 $0.00000 $0.00121

Measured 5d ago against content hash efae7bd6a45a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

review-simplify 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 5d 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.

.archon/workflows/sdlc/review/commands/review-simplify.md · 59 lines

How it starts

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

Simplify Review — The Smallest Coherent Shape

Writing code is cheap; maintaining it and recovering option value are not. Hunt one defect: the change delivers its required outcome through more structure than that outcome needs. Preserve meaningful invariants, supported behavior, and useful foundations — not accidental implementation shape. Read-only: never modify files, commit, or post anywhere.

Read $ARTIFACTS_DIR/review/scope.md first, and the project's architecture.md if it has one. Anchor the review on the accepted work order's stated invariants, and scale depth to what the change can destroy: irreversible or destructive paths, lifecycle ownership, persisted contracts and schemas, credentials and auth boundaries, integration boundaries, and concurrency over shared state each get an explicit attempt to refute the invariant they rest on; a prose-only change gets the minimum. In light mode, verify prior simplify findings first, then examine only the delta.

Establish the contract

Start with the exact diff scope.md records, against its base. Establish the intended outcome and invariants from the accepted work order, the PR, the changed files, their tests, and direct consumers. Read beyond the diff only as far as settling a concrete question requires. Existing code is evidence, not a mandate.

Test the structural decisions

Look first for decisions that add coordination or prematurely close options:

  • Data shape and ownership: Do core types match the dominant access paths? Is data copied, flattened, rebuilt, cached, or represented more than once when one owner could carry it?
  • Coherent capability: Does the change deepen one useful abstraction, or spread special-case coordination across callers, layers, and schemas?
  • Concurrency: If another actor changes shared state concurrently, is the answer safely "nothing"? If not, should the state be isolated instead of synchronized?
  • Foundations: Would one smaller primitive make the downstream logic obvious? Remove dead weight before adding scaffold; add scaffold early only when every later phase benefits from it.
  • Premature machinery: Which real supported variation requires each new state, lifecycle, wrapper, configuration surface, fallback, or extension point?

Read the full file on GitHub · 59 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. 5d ago First seen · 59 lines · 0 tokens per session scan A efae7bd6a45a

Subscribe to this mod's changes

review-simplify is a command published in the GitHub repository coleam00/Archon (23,374 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,210 tokens. 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.