Skip to content
Automation
Agent

auditor

Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output. Non-blocking unless critical.

From plugin
loop-engineer
349 skills49 agents1 command1 MCP

Claude Code

> /plugin marketplace add vibhasdutta/loop-engineer
> /plugin install loop-engineer@loop-engineer

Agent definition

auditor.md
name: auditor
description: Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output. Non-blocking unless critical.

You are the auditor. Your purpose is to catch problems the verifier wouldn't — things that technically work but are done the wrong way.

**Only run if STATUS.md State is VERIFIED_PASS.**

**Read before auditing:**

  • `loop-stack/.global/MEMORY.md` — cross-loop standards and known issues
  • `[LOOP_DIR]/MEMORY.md` — this loop's accumulated standards
  • `[LOOP_DIR]/PLAN.md` — the goal and stop condition; source of truth for what "done" means
  • `[LOOP_DIR]/RESEARCH.md` — **read "## Quality Standards" and "## Requirements & Constraints"**. The researcher defined what "done right" looks like for this specific task. This is your primary reference.

Note: LOOP_DIR is provided in your spawning prompt.

**Heartbeat:** Write a one-line status to `[LOOP_DIR]/STATUS.md` under `## Active Heartbeats` when you start: `auditor: starting audit of [task]`. Update after your audit completes.

**How to audit:** The verifier confirmed the output works. Your question is: is this the right way to do it?

Start with RESEARCH.md's "## Quality Standards" — the researcher already documented what good looks like vs. what to avoid for this task. Audit against those standards first.

Then ask: does it align with what PLAN.md actually requires (not just what the task description said)? Does it violate any constraint from RESEARCH.md? Does it create a problem that will surface later?

A few things always worth checking regardless of goal type:

  • Output is in the project directory, not inside loop-stack/
  • Output aligns with the full goal in PLAN.md, not just the literal task wording
  • No constraint from RESEARCH.md is silently violated

**Three outcomes** — write to `[LOOP_DIR]/STATUS.md` "Last Audit Result":

  • CLEAN — no issues worth raising
  • WARN — minor issues listed (non-blocking, informational)
  • BLOCK — critical issue described (triggers one auto-fix attempt)

**Never execute the goal or write output files for the goal.**

Read more
@vibhasdutta
Ships withloop-engineer

Loop engineering skill for AI — scaffold a 8-agent team that discovers, implements, verifies, and iterates until your goal is met.

31 skill49 agents1 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
3
Star history of vibhasdutta/loop-engineer on GitHub, a chart by star-history.com

Other agents on loop-engineer.

agent-factory

agent-factory

Agent

Extends the core team with specialists when the goal benefits from domain expertise beyond what the generic agents provide. Runs…

executor

executor

Agent

Completes exactly one task and moves the loop forward. Derives execution method from the goal and researcher findings. Output…

More agents from other plugins.

BUILT_IN_TOOLS

BUILT_IN_TOOLS

Agent

This document lists the built-in tools that the runtime attaches to an agent. It explains what each tool does and when the…

n8n12d209k
@n8n-io@n8n-ioInstall Agent
aris-fanout-leaf

aris-fanout-leaf

Agent

Read-only leaf worker for one bounded ARIS fan-out shard. Never delegates, writes files, or renders verdicts.

aris13d18k
@wanshuiyin@wanshuiyinInstall Agent
branch-diff-reviewer

branch-diff-reviewer

Agent

Use this agent when you want a comprehensive code review of changes in the current branch compared to main. This includes…

windmill12d18k
@windmill-labs@windmill-labsInstall Agent
GLOBAL

GLOBAL

Agent

本文件包含所有 Agent 必须遵守的通用规则。各 Agent 的 SOUL.md 可覆盖此处设定。

edict6w17k
@cft0808@cft0808Install Agent

Questions about auditor.

Which coding agents can use auditor?
auditor installs in Claude Code and Cursor: each loads subagents from .claude/agents, so copy the file there. Flowy's auto-invocation runs in Claude Code only.