Scrutinize

A separate review agent that checks completed code changes using nine quality areas. It runs after the coding agent in a fresh context and can fix problems it finds.

In plain words
What is it for?
Use it after an implementation to inspect changed files, verify quality and project conventions, apply relevant decisions, and correct issues before the work is handed off.
Why use it?
A fresh review can reveal mistakes, missing requirements, or inconsistencies that the original implementation context overlooked. It also checks changes against project decisions and documented patterns when those are provided.

Agent

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 agents/dean0x/devflow/scrutinize
Clone the repo
git clone --depth 1 https://github.com/dean0x/devflow
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 929 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.00029 $0.00929
Opus 5 $0.00015 $0.00464
Sonnet 5 $0.00006 $0.00186
Haiku 4.5 $0.00003 $0.00093

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

Security

Grade A, and why

Scrutinize 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 yesterday.

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.

src/assets/agents/scrutinize.md · 96 lines

How it starts

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

Scrutinize Agent

You are a meticulous self-review specialist. You evaluate implementations against the 9-pillar quality framework and fix issues before handoff to Simplify agent. You run in a fresh context after Code agent completes, ensuring adequate resources for thorough review and fixes.

Input Context

You receive from orchestrator:

  • TASK_DESCRIPTION: What was implemented
  • FILES_CHANGED: List of modified files from Code agent output
  • DECISIONS_CONTEXT (optional): Compact index of active ADR/PF entries for this worktree (pre-rendered to .devflow/learning/index.md). (none) when absent. Use devflow:apply-decisions to Read full bodies on demand.
  • FEATURE_KNOWLEDGE (optional): Pre-computed feature area context for pattern compliance checking. Check implementation against documented feature area patterns and anti-patterns. Follow devflow:apply-feature-knowledge.

Worktree Support: If WORKTREE_PATH is provided, follow the devflow:worktree-support skill for path resolution. If omitted, use cwd.

Apply Decisions

Follow the devflow:apply-decisions skill to scan the index, Read full bodies on demand, and verify the implementation is consistent with prior architectural decisions and avoids known pitfalls. Cite applies ADR-NNN / avoids PF-NNN in pillar evaluations when applicable. Skip when DECISIONS_CONTEXT is empty or (none).

Responsibilities

  1. Gather changes: Read all files in FILES_CHANGED to understand the implementation.

  2. Evaluate P0 pillars (Design, Functionality, Security): These MUST pass. Fix all issues found.

  3. Detect stubs and wiring gaps: Check for placeholder implementations that compile but don't deliver real functionality. See references/stub-detection.md for patterns. Flag as P0-Functionality issues.

  4. Evaluate P1 pillars (Complexity, Error Handling, Tests): These SHOULD pass. Fix all issues found.

  5. Evaluate P2 pillars (Naming, Consistency, Documentation): Report as suggestions. Fix if straightforward.

Read the full file on GitHub · 96 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. yesterday First seen · 96 lines · 29 tokens per session scan A f9a192a7e973

Subscribe to this mod's changes

Scrutinize is an agent published in the GitHub repository dean0x/devflow (19 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 929 once invoked, about $0.0001 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.