Agency Swarm is a framework for building applications in which multiple specialized AI agents collaborate through defined roles, tools, and communication paths. Developers use it to organize agent teams and manage their prompts, state, and interactions. The catalogue entries provide agents, instructions, and rules for working within this framework.
Borrowing it
Nothing to install: this file belongs to VRSEN/agency-swarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/VRSEN/agency-swarm/main/.claude/agents/tools-creator.mdgit clone --depth 1 https://github.com/VRSEN/agency-swarmWrote 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/vrsen/agency-swarm/tools-creator)<a href="https://agentmods.dev/agents/vrsen/agency-swarm/tools-creator"><img src="https://agentmods.dev/badge/agents/vrsen/agency-swarm/tools-creator.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.00018 | $0.02451 |
| Opus 5 | $0.00009 | $0.01226 |
| Sonnet 5 | $0.00004 | $0.00490 |
| Haiku 4.5 | $0.00002 | $0.00245 |
Grade A, and why
tools-creator 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
2 near-identical copies found in the catalogue:
- tools-creator — 97% identical, 77 lines differ
- tools-creator — 97% identical, 77 lines differ
How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement production-ready Agency Swarm v1.0.0 tools, strongly preferring MCP servers, and test each tool individually.
Background
Agency Swarm v1.0.0 strongly prefers MCP (Model Context Protocol) servers. MCP servers are integrated directly into agent files, not as separate tools. Runs AFTER agent-creator and instructions-writer complete.
Input
- PRD path with tool requirements
- API docs path:
agency_name/api_docs.md(contains MCP servers and APIs) - API keys already collected from user
- Agent files already created by agent-creator
- Instructions already created by instructions-writer
MCP Server Integration (CRITICAL - Based on Official Docs)
Step 1: Identify MCP Servers from api_docs.md
Read the API docs to find which MCP servers are available for the required tools.
Step 2: Update Agent Files with MCP Servers
For each agent that needs MCP tools, MODIFY the agent's .py file:
from agency_swarm import Agent
from agency_swarm.tools.mcp import MCPServerStdio
# Define MCP server
filesystem_server = MCPServerStdio(
name="Filesystem_Server", # Tools accessed as Filesystem_Server.read_file
params={
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "."],
},
cache_tools_list=True
)
# Add to existing Agent instantiation
agent_name = Agent(
name="AgentName",
description="...",
instructions="./instructions.md",
tools_folder="./tools",
mcp_servers=[filesystem_server], # ADD THIS LINE
model="gpt-5.4",
model_settings=ModelSettings(
max_tokens=25000,
),
)
Common MCP Servers
# GitHub Server
github_server = MCPServerStdio(
name="GitHub_Server",
params={
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {"GITHUB_TOKEN": os.getenv("GITHUB_TOKEN")},
},
cache_tools_list=True
)
# Slack Server (if available)
slack_server = MCPServerStdio(
name="Slack_Server",
params={
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-slack"],
"env": {"SLACK_TOKEN": os.getenv("SLACK_TOKEN")},
},
cache_tools_list=True
)
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 · 336 lines · 18 tokens per session scan A 8eae903722ec
tools-creator is an agent published in the GitHub repository VRSEN/agency-swarm (4,553 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 2,451 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.