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/shipwithai/shipwithai-plugins/setup-mcpnpx skills add ShipWithAI/shipwithai-plugins --skill setup-mcpgit clone --depth 1 https://github.com/ShipWithAI/shipwithai-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/shipwithai/shipwithai-plugins/setup-mcp)<a href="https://agentmods.dev/skills/shipwithai/shipwithai-plugins/setup-mcp"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/setup-mcp.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.00051 | $0.00846 |
| Opus 5 | $0.00026 | $0.00423 |
| Sonnet 5 | $0.00010 | $0.00169 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
setup-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 4d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup-mcp
Configures .mcp.json with MCP servers for external services.
Mode Detection
Read .claude/starter-context.json if it exists
→ Exists: use field mcp_selected — skip asking, go straight to lookup + write
→ Does not exist (standalone): ask "Which external services does your project use?"
Argument Handling
If a service name is passed directly (e.g. /setup-mcp github): skip the service selection
prompt and go straight to lookup for that service.
Service Lookup
Load mcp-registry.json and show the available services:
GitHub → code search, PR management, issues
Linear → issue tracking, sprint planning
Slack → search messages, read channels
Sentry → error tracking, performance data
PostgreSQL → direct DB queries, schema inspection
Google Drive → search and read documents
Notion → read and search pages and databases
Jira → issue tracking, sprint management
For each selected service:
- Look up config in the registry.
- If
authRequiredis true: show auth requirement before writing:"This server requires [authNote]. Do you have credentials ready?" If no: offer to skip and add later.
- If service type is
stdio: ask for required runtime values (e.g. connection string) before writing — never write placeholder values literally. - Show config preview (see Output Format below).
- Attempt test connection after writing (see Verification below).
- Confirm before writing.
If the requested service is not in the registry: do not fabricate a config. Ask the user to paste an MCP URL if they have one, or skip for now.
Output Format
If .mcp.json does not exist: create it with { "mcpServers": {} }.
HTTP server:
{
"mcpServers": {
"github": {
"url": "https://api.githubcopilot.com/mcp/",
"type": "http",
"description": "Search code, manage PRs and issues"
}
}
}
stdio server (e.g. PostgreSQL — ask user for connection string first):
{
"mcpServers": {
"postgres": {
"command": "npx",
"args": ["@modelcontextprotocol/server-postgres", "postgresql://user:pass@host/db"],
"description": "Direct database queries and schema inspection"
}
}
}
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 109 lines · 51 tokens per session scan A c1684a7d6cc7
setup-mcp is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 22d ago), licensed MIT. It adds 51 tokens to every session and 846 once invoked, about $0.0003 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
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
espalier-migrate
Migrate an existing harness/espalier install to the current Espalier version — auto-detects which of v0.1→v0.2, v0.3→v0.4, v0.4→v0.5, the v0.5.3 coder-agent patch, v0.5→v0.6 (Stage 1 grill), v0.6→v0.7 (read-only /espalier-ask lane), v0.7→v0.8 (requirements approval gate), the v0.8.1 impact-analysis agent patch, the…
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…
session-mode
Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.