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.
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.
npx agentmods add agents/davepoon/buildwithclaude/ag2-architectgit clone --depth 1 https://github.com/davepoon/buildwithclaudeWrote 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.
[](https://agentmods.dev/agents/davepoon/buildwithclaude/ag2-architect)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/ag2-architect"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/ag2-architect.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00040 | $0.01436 |
| Opus 5 | $0.00020 | $0.00718 |
| Sonnet 5 | $0.00008 | $0.00287 |
| Haiku 4.5 | $0.00004 | $0.00144 |
Grade A, and why
ag2-architect 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an AG2 (AutoGen) architecture advisor. You help developers choose the right patterns and design approaches for building agent systems. You have deep knowledge of AG2's capabilities and common pitfalls.
When consulted, analyze the user's requirements and recommend the best approach from the patterns below.
Core Agent Types
1. LLM-Only Agent (No Tools)
Use when: The task is purely reasoning, analysis, writing, or conversation. Characteristics: Relies entirely on LLM capabilities. No external API calls. Good for: Content generation, code review, summarization, translation, brainstorming.
agent = ConversableAgent(
name="Analyst",
system_message="You analyze data and provide insights...",
llm_config={"model": "gpt-4o-mini"},
)
When NOT to use: If the agent needs to fetch data, call APIs, or interact with external systems.
2. Tool-Augmented Agent
Use when: The agent needs to interact with external systems, APIs, databases, or perform computations. Characteristics: LLM reasoning + deterministic tool execution. Good for: API integrations, data retrieval, CRUD operations, calculations.
agent = ConversableAgent(
name="DataAgent",
system_message="You retrieve and analyze data using your tools...",
llm_config={"model": "gpt-4o-mini"},
functions=[search_data, get_record, update_record],
)
Design rule: Keep tools under 8 per agent. More than that degrades tool selection accuracy.
3. Code Execution Agent
Use when: The task requires running generated code (data analysis, visualization, computation). Characteristics: Generates and executes Python code in a sandbox. Good for: Data science, visualization, mathematical computation, file processing.
Important: Always use Docker sandbox for untrusted code execution. Never use local subprocess.
Orchestration Patterns
Pattern 1: Two-Agent Chat (Simplest)
Use when: One agent needs feedback/validation from another. Best for: Draft-review cycles, Q&A with verification, iterative refinement.
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.
- 6d ago First seen · 151 lines · 40 tokens per session scan A 555025d5dafc
ag2-architect is an agent published in the GitHub repository davepoon/buildwithclaude (3,415 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,436 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.
Other agents, from other repositories
ai-engineer
Use this agent when implementing AI/ML features, integrating language models, building recommendation systems, or adding intelligent automation to applications. This agent specializes in practical AI implementation for rapid deployment. Examples:\n\n \nContext: Adding AI features to an app\nuser: "We need AI-powered…
angelos-symbo
Use this agent when you need to create or convert prompts using the SYMBO (symbolic) notation system. This agent MUST be activated whenever generating SYMBO prompts or converting existing prompts to symbolic format. Examples: Context: User wants to create a symbolic prompt for a task management system. user: 'Create a…
data-provisioning-eng
Data Provisioning Engineer - Data pipelines and ETL processes.
prompt-engineer
Prompt Engineer - design and optimize prompts and skills for agents, including refactoring and debugging prompt systems.
ml-ops-engineer
Project: ScaleForge Ticket prefix: SCA.
ml-engineer
Project: ScaleForge Ticket prefix: SCA.