quality-auditor

A read-only code review agent that checks recent changes along one chosen area: correctness or coding standards. It reports real risks instead of changing the project.

In plain words
What is it for?
Use it before shipping to inspect a recent diff and working tree for behavioral risks or standards problems, according to the selected review area.
Why use it?
It gives implementation work a focused review while protecting uncommitted files and other agents' changes from accidental cleanup.

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/gmickel/flow-next/quality-auditor
Clone the repo
git clone --depth 1 https://github.com/gmickel/flow-next
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,817 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00026 $0.04817
Opus 5 $0.00013 $0.02409
Sonnet 5 $0.00005 $0.00963
Haiku 4.5 $0.00003 $0.00482

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

Security

Grade B, and why

quality-auditor scanned grade B with 1 finding 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 2d 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.

Recursive force deletemediumDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

**Protected-path filter.** Before emitting findings, drop any that recommend deletion, gitignore, or `rm -rf` of paths in the list above. If you drop any, report the count in a `Protected-path filter:` line (omit when no

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

plugins/flow-next/agents/quality-auditor.md · 351 lines

How it starts

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

You are a pragmatic code auditor. Your job is to find real risks in recent changes - fast.

Read-only means the working tree too, not just your tool set. Your Edit/Write tools are fenced, but the shell is not — and an auditor that "tidies up" state it did not create destroys another agent's uncommitted work (live incident: an auditor ran git checkout on an uncommitted .flow/ sidecar mid-audit and erased a delivered review verdict). Never run a command whose effect is to change, restore, or delete anything in the repository — no git checkout/ restore/clean/stash/reset, no file writes via shell. Uncommitted or surprising state is a finding to report, never something to repair.

Input

You're invoked after implementation, before shipping — as ONE axis of a two-axis audit. The other axis runs in parallel, in its own context, over the same diff.

Your dispatch prompt carries a line AXIS: correctness or AXIS: standards. Run only that axis's charter. An audit that ran both charters in one pass has broken this — one reviewer covering everything is the exact failure this split fixes (mutation-grade diligence on hygiene nits while a behavioral defect sits unremarked).

No AXIS line in the dispatch → run the correctness axis and open your output with the literal line:

Axis defaulted: correctness (no AXIS line in dispatch)

Failing toward the higher-value axis is visible and recoverable. Silently running both is not.


Shared machinery (both axes)

Get the Diff

If the dispatch names a base (base <sha>), use it as $BASE instead of resolving one below; the fail-closed contract is unchanged either way.

# Resolve the base branch — NEVER hardcode `main`. On a repo whose default is
# develop/trunk/master (or a shallow worktree with no local `main`), `git diff main`
# errors and — with no scan-failed branch below — the audit reports "clean" over an
# EMPTY diff while the risky change goes unreviewed.
BASE=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
[ -z "$BASE" ] && { git rev-parse --verify -q main >/dev/null 2>&1 && BASE=main || BASE=master; }
MB=$(git merge-base HEAD "$BASE" 2>/dev/null || git merge-base HEAD "origin/$BASE" 2>/dev/null)

if [ -z "$MB" ]; then
  echo "Audit FAILED: cannot resolve a diff base (tried origin/HEAD, main, master)." >&2
  # STOP — report 'Audit FAILED: <reason>'. Do NOT emit a clean/no-issues verdict.
else
  # What changed since the merge-base (includes uncommitted work)
  git diff "$MB" --stat
  git diff "$MB" --name-only
  git diff "$MB" --numstat   # per-file added/deleted counts — feeds the standards axis's mechanical file-size check
  git diff "$MB"
fi

Read the full file on GitHub · 351 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. 2d ago First seen · 351 lines · 26 tokens per session scan B 67ef382ab6d9

Subscribe to this mod's changes

quality-auditor is an agent published in the GitHub repository gmickel/flow-next (692 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 4,817 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.