coding-review-agent-loop CLAUDE.md

Instructions for a coding-review agent loop that coordinates work on issues and pull requests with one or more reviewers. A pull request is a proposed code change submitted for review before it is merged.

In plain words
What is it for?
Use it to run a review loop for an issue or pull request, choose reviewers, use plan-first mode, fix review blockers, or resume an interrupted run.
Why use it?
They define the required inputs and workflow so an automated review-and-fix cycle starts consistently instead of relying on informal prompts.

Instructions file

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 instructions/wwind123/coding-review-agent-loop/claude-md
Clone the repo
git clone --depth 1 https://github.com/wwind123/coding-review-agent-loop
Per session 278 This file is loaded in full into every session.
When invoked 278 The same file — it is already loaded in full.
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.00278 $0.00278
Opus 5 $0.00139 $0.00139
Sonnet 5 $0.00056 $0.00056
Haiku 4.5 $0.00028 $0.00028

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

Security

Grade A, and why

coding-review-agent-loop CLAUDE.md 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 3d 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.

CLAUDE.md · 30 lines

What it actually says

coding-review-agent-loop — Claude Code Instructions

Skill mode

When a user asks you to run the agent loop for an issue or PR, load and follow the instructions in SKILL.md.

Slash command (preferred): the user can type /coding-review-agent-loop followed by arguments — Claude Code loads .claude/commands/coding-review-agent-loop.md which prompts you to read SKILL.md and start orchestration.

Natural language also works:

  • "Run the agent-loop skill for issue #123 in OWNER/REPO with gemini as reviewer"
  • "Start agent-loop plan-first for issue #42, reviewers: codex and gemini"
  • "Run agent-loop pr 99 in OWNER/REPO"
  • "Have codex fix the blocking review on PR #99 in OWNER/REPO"
  • "Resume the agent-loop skill for issue #123"

In every case: read SKILL.md, gather the required inputs (repo, issue/PR number, reviewers, flow type), and follow the orchestration steps from the top.

Development

The main package lives in src/coding_review_agent_loop/. Tests are in tests/. Run the full test suite with:

.venv/bin/python -m pytest tests/ -q
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. 3d ago First seen · 30 lines · 278 tokens per session scan A d509a1cac46e

Subscribe to this mod's changes

coding-review-agent-loop CLAUDE.md is an instructions file published in the GitHub repository wwind123/coding-review-agent-loop (11 stars, last pushed 5d ago), licensed MIT. It adds 278 tokens to every session, about $0.0014 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens