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 commands/vrsen/openswarm/add-mcpgit clone --depth 1 https://github.com/VRSEN/OpenSwarmWhat 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.00000 | $0.04691 |
| Opus 5 | $0.00000 | $0.02346 |
| Sonnet 5 | $0.00000 | $0.00938 |
| Haiku 4.5 | $0.00000 | $0.00469 |
Grade A, and why
add-mcp 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 yesterday.
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:
- add-mcp — 89% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 629 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Creation Task
Your task is to add Model Context Protocol (MCP) server to an Agency Swarm agent. MCP servers expose external tools and data sources to agents through a standardized protocol.
Quick Reference: MCP Server Types
| Server Type | When to Use | URL Pattern | Class to Use |
|---|---|---|---|
| Hosted Remote | Publicly accessible web service | Any public URL | HostedMCPTool |
| Hosted Remote (OAuth) | Publicly accessible web service with OAuth | Any public URL | MCPServerStdio + mcp-remote |
| Streamable HTTP | HTTP streaming server | Ends in /mcp |
MCPServerStreamableHttp |
| SSE | Server-Sent Events server | Ends in /sse |
MCPServerSse |
| Local/Stdio | GitHub repo, local script, or CLI tool | GitHub URL or local path | MCPServerStdio |
Step-by-Step Process
Step 1: Determine Server Type
If user provides a URL:
- Check if it's a public/internet-accessible URL:
- Requires OAuth authentication? → Use
mcp-remotewithMCPServerStdio - No authentication or token-based auth? → Use
HostedMCPTool
- Requires OAuth authentication? → Use
- Check if URL ends with
/mcp→ UseMCPServerStreamableHttp(orHostedMCPToolif public) - Check if URL ends with
/sse→ UseMCPServerSse(orHostedMCPToolif public)
If user provides a GitHub URL or mentions "local":
- Use
MCPServerStdio
If unclear, ask:
- Is this a publicly accessible URL? (HostedMCPTool or mcp-remote)
- Does it require OAuth authentication? (Use mcp-remote)
- Is this a local server you'll run? (MCPServerStdio, MCPServerSse, or MCPServerStreamableHttp)
- What's the server endpoint URL? (check
/mcpor/ssesuffix) - Which agent do you want to add this MCP server to?
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.
- yesterday First seen · 629 lines · 0 tokens per session scan A 1755d2188e6b
add-mcp is a command published in the GitHub repository VRSEN/OpenSwarm (2,856 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,691 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.