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 skills/ag2ai/ag2-claude-plugins/nested-chatnpx skills add ag2ai/ag2-claude-plugins --skill nested-chatgit 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/nested-chat)<a href="https://agentmods.dev/skills/ag2ai/ag2-claude-plugins/nested-chat"><img src="https://agentmods.dev/badge/skills/ag2ai/ag2-claude-plugins/nested-chat.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 | $0.00047 | $0.00875 |
| Opus 5 | $0.00023 | $0.00438 |
| Sonnet 5 | $0.00009 | $0.00175 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
nested-chat 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.
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 creating an AG2 nested chat workflow. This encapsulates a multi-step pipeline inside a single agent using register_nested_chats.
Instructions
-
Ask the user for:
- The pipeline stages and what each agent does
- The trigger condition (which sender activates the nested pipeline)
- How results pass between stages (
summary_method)
-
Create the nested chat following this pattern:
Nested Chat Pattern
import asyncio
from autogen import ConversableAgent, LLMConfig
llm_config = LLMConfig({"api_type": "anthropic", "model": "claude-sonnet-4-6"})
user = ConversableAgent(
name="user",
human_input_mode="NEVER",
)
# The outer agent that encapsulates the pipeline
coordinator = ConversableAgent(
name="coordinator",
system_message="Present the final result.",
llm_config=llm_config,
)
# Pipeline stage agents
step_1 = ConversableAgent(
name="step_1",
system_message="Do the first step.",
llm_config=llm_config,
)
step_2 = ConversableAgent(
name="step_2",
system_message="Do the second step.",
llm_config=llm_config,
)
step_3 = ConversableAgent(
name="step_3",
system_message="Do the third step.",
llm_config=llm_config,
)
# Register the nested pipeline -- fires when coordinator receives from user
coordinator.register_nested_chats(
chat_queue=[
{
"recipient": step_1,
"message": lambda recipient, messages, sender, config: messages[-1]["content"],
"max_turns": 1,
"summary_method": "last_msg",
},
{
"recipient": step_2,
"message": "Continue with the second step.",
"max_turns": 1,
"summary_method": "last_msg",
},
{
"recipient": step_3,
"message": "Complete the third step.",
"max_turns": 1,
"summary_method": "last_msg",
},
],
trigger=user, # fires when message comes from user
)
async def main():
response = await user.a_run(
coordinator,
message="Your task here",
max_turns=1,
)
await response.process()
print(await response.summary)
if __name__ == "__main__":
asyncio.run(main())
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.
- 3d ago First seen · 118 lines · 47 tokens per session scan A 81844771d49d
nested-chat is a skill published in the GitHub repository ag2ai/ag2-claude-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 875 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…