ag2-reviewer

ag2-reviewer is an agent for Claude Code from davepoon/buildwithclaude. It costs 34 tokens per session (643 once invoked), scanned A, original, MIT.

A reviewer for AG2, a Python framework for building cooperating AI agents. It checks agent code, tool definitions, prompts, error handling, security, and configuration.

In plain words
What is it for?
Use it after creating or changing AG2 agents to check tool return formats, parameter annotations, exception handling, credential handling, input validation, naming, and prompt quality.
Why use it?
It catches contract violations and unsafe patterns before an agent is used or deployed.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Part of the ag2-agent-builder plugin — 7 commands, 3 agents shipped together

Good fit Use it after creating or changing AG2 agents to check tool return formats, parameter annotations, exception handling, credential handling, input validation, naming, and prompt quality.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/davepoon/buildwithclaude/ag2-reviewer
About the project

davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.

davepoon/buildwithclaude · 3,429 stars · on GitHub · buildwithclaude.com

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.

Clone the repo
git clone --depth 1 https://github.com/davepoon/buildwithclaude

Made for: Claude Code.

Or install ag2-agent-builder, the plugin that ships this one along with the rest of its 7 commands, 3 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ag2-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/davepoon/buildwithclaude/ag2-reviewer.svg)](https://agentmods.dev/agents/davepoon/buildwithclaude/ag2-reviewer)
Your own site
<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/ag2-reviewer"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/ag2-reviewer.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 643 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00034 $0.00643
Opus 5 $0.00017 $0.00321
Sonnet 5 $0.00007 $0.00129
Haiku 4.5 $0.00003 $0.00064

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

Security

Grade A, and why

ag2-reviewer 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 9d 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.

plugins/ag2-agent-builder/agents/ag2-reviewer.md · 78 lines

How it starts

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

You are an expert reviewer of AG2 (AutoGen) agent implementations. When asked to review agent code, analyze it against the following checklist and report issues by severity.

Review Checklist

Critical Issues (must fix)

Tool Contract Violations:

  • Tool functions must return str (JSON string), not dict or other types
  • Return format must be {"success": bool, "data": ...} or {"success": bool, "error": "..."}
  • All tool parameters must have type annotations
  • All tool functions must have docstrings with Args: section

Error Handling:

  • Tool functions must never raise unhandled exceptions
  • Must catch specific exceptions before generic Exception
  • Missing credentials must return connector_setup_required:<id>, not raise

Security:

  • No hardcoded API keys, tokens, or secrets
  • No unsafe dynamic code execution with user input
  • Input validation on parameters that become part of URLs or queries
  • No SQL injection vectors in database tools

Important Issues (should fix)

Agent Configuration:

  • name should be PascalCase and descriptive
  • description should be a concise one-liner (used for routing/discovery)
  • system_message should clearly define role, capabilities, and boundaries
  • llm_config should specify a model explicitly (no implicit defaults)

System Prompt Quality:

  • Does the prompt define what the agent IS? (role)
  • Does the prompt define what the agent CAN DO? (capabilities)
  • Does the prompt define what the agent SHOULD NOT DO? (boundaries)
  • Does the prompt specify output format expectations?
  • Is the prompt specific enough to avoid confusion with other agents?

Tool Design:

  • Are tool docstrings specific enough for the LLM to know when to use them?
  • Are there too many tools? (>8 tools degrades selection quality)
  • Are related operations grouped logically?
  • Do tools have sensible parameter defaults?

Recommendations (nice to have)

Multi-Agent Coordination:

  • If in a group chat, does each agent have a distinct role?
  • Are termination conditions clear?
  • Is max_round or max_turns set to prevent runaway conversations?

Read the full file on GitHub · 78 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. 9d ago First seen · 78 lines · 34 tokens per session scan A b5bd098a1d3a

Subscribe to this mod's changes

ag2-reviewer is an agent published in the GitHub repository davepoon/buildwithclaude (3,429 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 643 once invoked, about $0.0002 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 agents, from other repositories

prompt-engineer

Use this agent when the user needs to create, modify, review, or optimize system prompts for AI agents or language models. This includes requests to improve prompt effectiveness, add specific behaviors, refine instructions, or evaluate existing prompts for clarity and performance. Examples:\n\n \nContext: The user…

sonomirco/agents-and-commands · 0 tokens

rag-pipeline-reviewer

Reviews RAG (Retrieval-Augmented Generation) pipelines for retrieval quality, chunking strategy, embedding choices, and evaluation coverage. Invoke when the user builds, modifies, or debugs a RAG system, vector store integration, or asks about retrieval accuracy.

affaan-m/ECC · 58 tokens

Project Recon

Fast, high-level survey that orients the security agents — what the project is, its stack, auth model, integrations, and notable areas.

agentgg-dev/agentgg · 32 tokens

code-reviewer

Code Reviewer - SDD per-task review (L2) + codebase audit execution (audit). Read-only seat: does not implement, fix, or occupy a QC seat.

btspoony/mstar-harness · 40 tokens

logic-design

Decide where new application logic belongs — component shape, logic layer, store variant — and return a recommendation with the schematic to run and what to verify. Use the logic-review agent for existing code.

AmadeusITGroup/otter · 43 tokens

FAI Enterprise RAG Reviewer

Enterprise RAG reviewer — RAG quality audit, citation accuracy, search config validation, security compliance, OWASP LLM Top 10, and WAF pillar alignment checks.

frootai/frootai · 42 tokens