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/shipwithai/shipwithai-plugins/add-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/commands/shipwithai/shipwithai-plugins/add-mcp)<a href="https://agentmods.dev/commands/shipwithai/shipwithai-plugins/add-mcp"><img src="https://agentmods.dev/badge/commands/shipwithai/shipwithai-plugins/add-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.00043 | $0.00334 |
| Opus 5 | $0.00022 | $0.00167 |
| Sonnet 5 | $0.00009 | $0.00067 |
| Haiku 4.5 | $0.00004 | $0.00033 |
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 5d 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.
What it actually says
/add-mcp
Add a single MCP server to .mcp.json. Stateless — no init context required.
Steps
-
If user provides a service name → look up in the plugin's
mcp-registry.json(located atskills/setup-mcp/mcp-registry.jsonin the plugin directory).- Found: show preset config, confirm.
- Not found: "Paste the MCP URL and a short description."
-
Show config preview before writing:
{ "mcpServers": { "[name]": { "url": "...", "description": "..." } } } -
If
authRequiredis true in the registry entry: surface auth requirement before writing. Ask: "This server requires [authNote]. Do you have credentials ready?" -
Attempt test connection → report ✓ tested / ⚪ configured-not-verified / ✗ not-found. Never report ✓ without actually testing. MCP servers load at next Claude Code startup.
-
Confirm → append to
.mcp.json. Check for duplicateidbefore writing — skip if already present. -
Update
**Last updated:**date in the Harness config section ofCLAUDE.mdif the file exists.
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.
- 5d ago First seen · 42 lines · 43 tokens per session scan A 1468eb690121
add-mcp is a command published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 23d ago), licensed MIT. It adds 43 tokens to every session and 334 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 commands, from other repositories
debug
Systematic debugging with hypotheses and evidence gathering.
whats-next
Show current project status and suggest next steps.
review
Run a Codex code review of your working tree or a branch (read-only).
explore
Fast codebase exploration with Antigravity's agy CLI (Gemini 3.7 Flash, read-only). EXPERIMENTAL.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.