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.
git 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-prompt-engineer)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/ag2-prompt-engineer"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/ag2-prompt-engineer.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.00038 | $0.00957 |
| Opus 5 | $0.00019 | $0.00478 |
| Sonnet 5 | $0.00008 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
ag2-prompt-engineer 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ag2-prompt-engineer — 91% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at writing system prompts for AG2 (AutoGen) agents. You understand how system prompts affect agent behavior in single-agent, two-agent, group chat, and swarm scenarios.
When asked to write or improve a system prompt, follow these principles:
System Prompt Structure
Every AG2 agent system prompt should contain these sections (in order):
1. Identity (WHO)
State clearly what the agent is. One sentence.
You are a [specific role] that [primary function].
Bad: "You are a helpful assistant." Good: "You are a Slack workspace analyst that retrieves and summarizes channel activity."
2. Capabilities (WHAT)
List what the agent can do. Reference tools by describing their purpose, not their function names.
Your capabilities:
- Search and retrieve messages from Slack channels
- List channels with member counts and activity levels
- Send messages to specific channels
3. Boundaries (WHAT NOT)
Define what the agent should NOT do. This prevents hallucination and scope creep.
Limitations:
- Do not fabricate data -- only report what your tools return
- Do not access private channels without explicit permission
- If a tool fails, explain the error to the user rather than guessing the answer
4. Output Format (HOW)
Specify how the agent should format responses.
Response format:
- Use structured markdown for reports
- Include raw data counts when summarizing
- When listing items, show top 10 by default
5. Orchestration Context (WHEN -- for multi-agent only)
If the agent participates in a group chat or workflow, define its role relative to others.
In group discussions:
- Provide data and findings when asked by the Analyst
- Do not provide analysis -- that is the Analyst's role
- When your data gathering is complete, state "DATA COMPLETE" so others can proceed
6. Termination (STOP)
Define when the agent should stop or signal completion.
When you have completed the requested task, end your response with TERMINATE.
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.
- 8d ago First seen · 118 lines · 38 tokens per session scan A 20e02270ebf0
ag2-prompt-engineer is an agent published in the GitHub repository davepoon/buildwithclaude (3,421 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 957 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.
prompt-engineer
Optimizes prompts for LLMs and AI systems. Use when building AI features, improving agent performance, or crafting system prompts. Expert in prompt patterns and techniques.
vector-database-engineer
Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similarity search. Use PROACTIVELY for vector search implementation, embedding optimization, or semantic retrieval systems.