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 skills add ag2ai/ag2-claude-plugins --skill new-agentgit clone --depth 1 https://github.com/ag2ai/ag2-claude-pluginsWrote 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/skills/ag2ai/ag2-claude-plugins/new-agent)<a href="https://agentmods.dev/skills/ag2ai/ag2-claude-plugins/new-agent"><img src="https://agentmods.dev/badge/skills/ag2ai/ag2-claude-plugins/new-agent.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.00035 | $0.00558 |
| Opus 5 | $0.00017 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
new-agent 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 7d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are scaffolding a new AG2 (AutoGen) agent. Follow the AG2 framework patterns exactly.
Instructions
-
Ask the user for:
- Agent name and purpose
- What tools/capabilities it needs
- Which LLM model to use (default: gpt-4o-mini)
- Whether it needs external API access
-
Create the agent following this exact structure:
File Structure
agents/<agent-name>/
<agent_name>.py # Agent definition + tools
README.md # Capabilities documentation
Agent Code Pattern
import json
from autogen import ConversableAgent, LLMConfig
from autogen.tools import tool
# --- Tool Functions ---
# Each tool returns a JSON string with {"success": bool, "data": ..., "error": ...}
@tool()
def tool_name(param1: str, param2: int = 10) -> str:
"""Clear description of what this tool does.
Args:
param1: Description of param1
param2: Description of param2 (default: 10)
"""
try:
# Implementation
result = {"key": "value"}
return json.dumps({"success": True, "data": result})
except Exception as e:
return json.dumps({"success": False, "error": str(e)})
# --- Agent Definition ---
agent = ConversableAgent(
name="agent_name",
description="One-line description for orchestrator routing",
system_message="""You are a [role description].
Your capabilities:
- Capability 1
- Capability 2
Guidelines:
- Always use the appropriate tool for the task
- Return structured responses
- Handle errors gracefully and explain what went wrong
""",
llm_config=LLMConfig({"api_type": "anthropic", "model": "claude-sonnet-4-6"}),
functions=[tool_name],
)
Key Rules
- Tool functions MUST have docstrings (used for LLM function calling schema)
- System messages should be specific about the agent's role and boundaries
- Agent
descriptionis used by orchestrators to route tasks -- keep it concise - Use
@tool()decorator fromautogen.tools - Group related tools in the same file
- Never use bare
except:-- always catch specific exceptions orException
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.
- 7d ago First seen · 80 lines · 35 tokens per session scan A 8aa492c3e917
new-agent is a skill published in the GitHub repository ag2ai/ag2-claude-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 558 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…