agent-factory
AgentExtends the core team with specialists when the goal benefits from domain expertise beyond what the generic agents provide. Runs…
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.
Claude Code
> /plugin marketplace add vibhasdutta/loop-engineer> /plugin install loop-engineer@loop-engineer
Cursor
Cursor also loads subagents from .claude/agents, so copy this file there to use it in Cursor.
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:**
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:
**Three outcomes** — write to `[LOOP_DIR]/STATUS.md` "Last Audit Result":
**Never execute the goal or write output files for the goal.**
Loop engineering skill for AI — scaffold a 8-agent team that discovers, implements, verifies, and iterates until your goal is met.
Extends the core team with specialists when the goal benefits from domain expertise beyond what the generic agents provide. Runs…
Completes exactly one task and moves the loop forward. Derives execution method from the goal and researcher findings. Output…
This is a reference for the researcher agent. Read the goal and current task, identify which categories apply, then pull sources…
- Google Search - Bing Search - Brave Search - DuckDuckGo - Kagi - Mojeek - Yahoo Search - Yandex - SearXNG - Startpage
- GitHub - GitLab - Bitbucket - SourceForge - Codeberg
- MDN - DevDocs - ReadTheDocs - Dash Docs - Zeal Docs
Read-only leaf worker for one bounded ARIS fan-out shard. Never delegates, writes files, or renders verdicts.
Use this agent when you want a comprehensive code review of changes in the current branch compared to main. This includes…