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.
git 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-agent)<a href="https://agentmods.dev/commands/shipwithai/shipwithai-plugins/add-agent"><img src="https://agentmods.dev/badge/commands/shipwithai/shipwithai-plugins/add-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/shipwithai/shipwithai-plugins/add-agent"><img src="https://agentmods.dev/badge/commands/shipwithai/shipwithai-plugins/add-agent.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.00498 |
| Opus 5.5 | $0.00016 | $0.00199 |
| Sonnet 5.5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
add-agent 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 2mo 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-agent
Create a new agent in .claude/agents/. Stateless.
Steps
-
Check the plugin's
agents-catalog.json(located atskills/setup-agents/agents-catalog.jsonin the plugin directory) for a match with the user's intent.- Match: show preset, confirm or customize.
- No match: ask:
- Agent name and purpose?
- Context type: autonomous (self-orients by reading files) or task-specific (needs input from caller)?
- Model: haiku (fast, read-only tasks) / sonnet (analysis, code review) / opus (complex reasoning)?
- Tools needed: Read, Bash, Glob, Grep, WebFetch?
- For autonomous: which files does it read on startup?
- For task-specific: what parameters must the caller pass in the prompt?
- Trigger phrases to invoke this agent?
-
Draft agent file using the standard format:
--- name: [name] description: > [purpose + trigger phrases] model: [haiku|sonnet|opus] tools: ["Read", "Bash", "Glob", "Grep"] --- # [Agent Name] ## Purpose [Why this agent exists. What problem it solves.] ## Context **Reads on startup:** - [files this agent reads to orient itself] **Expects in prompt:** *(task-specific agents only)* - [PARAM_NAME]: [description and how to pass it] ## Steps ### Step 1 — [Action] [Description] ## Boundaries - Does not modify files directly - Does not self-schedule -
Show preview → confirm → write
.claude/agents/[name].md. If file already exists: offer skip or overwrite, do not silently replace. -
Note: "Claude Code agents do not self-schedule. Set up a crontab manually if needed."
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.
- 2mo ago First seen · 67 lines · 40 tokens per session scan A d13abdb7debe
add-agent is a command published in the GitHub repository ShipWithAI/shipwithai-plugins (9 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 498 once invoked, about $0.0002 per session on Opus 5.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.
add-agent compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| add-agentShipWithAI/shipwithai-plugins | Command | 9 | 2mo ago | MIT | A | 40 | Claude Code |
| debugprimeline-ai/evolving-lite | Command | 50 | 1mo ago | MIT | A | 8 | Claude Code |
| ccc-orchestrateKevinZai/commander | Command | 6 | today | MIT | A | 53 | Claude Code |
| ccc-themeKevinZai/commander | Command | 6 | today | MIT | A | 47 | Claude Code |
| ccc-auditKevinZai/commander | Command | 6 | today | MIT | A | 45 | Claude Code |
| specmanager-buildjoanseg/specmanager | Command | 27 | 6d ago | MIT | B | 25 | Claude Code |
| executeskullninja/coco-workflow | Command | 7 | 26d ago | MIT | A | 28 | Claude Code |