Borrowing it
Nothing to install: this file belongs to chacosoldier/compabob. 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/chacosoldier/compabob/main/.claude/skills/add-agent/SKILL.mdgit clone --depth 1 https://github.com/chacosoldier/compabobWrote 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/chacosoldier/compabob/add-agent)<a href="https://agentmods.dev/skills/chacosoldier/compabob/add-agent"><img src="https://agentmods.dev/badge/skills/chacosoldier/compabob/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/skills/chacosoldier/compabob/add-agent"><img src="https://agentmods.dev/badge/skills/chacosoldier/compabob/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.00035 | $0.00488 |
| Opus 5.5 | $0.00014 | $0.00195 |
| Sonnet 5.5 | $0.00007 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
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 1mo 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 so the assistant grows with the user's work. This is the main way to customize the kit.
Steps
- Ask four things (one short round of questions, not an interrogation):
- Name: kebab-case, e.g.
recruitingorproduct-research. - Purpose and triggers: what it owns, and the phrases or domains that should route to it. This becomes the
description, which is what actually drives routing. - Tools: the minimum it needs (4 to 6). Advice-only agents get read tools only:
Read, Glob, Grep, WebFetch, WebSearch. - Model:
inheritis the default (the agent follows the session's model); pinsonnetfor a cheap, high-volume agent oropusfor one that always needs hard reasoning.
- Name: kebab-case, e.g.
- Check for overlap. Read the existing agents in
.claude/agents/. If the new agent overlaps an existing one, say so and suggest either editing the existing agent or sharpening both descriptions so routing stays clean. - Scaffold. Copy
.claude/agents/_agent-template.md.templateto.claude/agents/<name>.mdand fill it in: frontmatter, Purpose, When to use / when not to, Output format, Safety. - Register it. Add a one-line routing rule for the new agent to the Agent Architecture & Routing section of
CONSTITUTION.md. (_orchestrator-reference.mddescribes coordination patterns; it is not a list of agents.) - Test routing. Suggest two or three prompts that should land on the new agent, and one that should not (to confirm it does not over-trigger).
Principles
- The
descriptionis the routing signal. Write it as "Use for X, Y, Z", and name what it is not for. - Keep the tool list minimal. An agent with every tool routes badly.
- One agent, one job. If it needs a paragraph to describe, it is two agents.
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.
- 1mo ago Changed d76cc0000ecc
- 1mo ago First seen · 27 lines · 35 tokens per session scan A cd07b4752655
add-agent is a skill published in the GitHub repository chacosoldier/compabob (34 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 488 once invoked, about $0.0001 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-30.
Other skills, from other repositories
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
media-processing
Ingest and process media files (video, audio, image).
notifications
Send notifications through the unified notification router.
visualize
Render a polished visual inline in the chat as part of your answer — a diagram, a chart, an interactive explainer, or a UI mockup. Load it proactively whenever an explanation would land better as a picture than as prose. Do not wait to be asked.