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 skills add stefan-jansen/coding-agent-toolkit --skill delegategit clone --depth 1 https://github.com/stefan-jansen/coding-agent-toolkitWrote 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/stefan-jansen/coding-agent-toolkit/delegate)<a href="https://agentmods.dev/skills/stefan-jansen/coding-agent-toolkit/delegate"><img src="https://agentmods.dev/badge/skills/stefan-jansen/coding-agent-toolkit/delegate/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/stefan-jansen/coding-agent-toolkit/delegate"><img src="https://agentmods.dev/badge/skills/stefan-jansen/coding-agent-toolkit/delegate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00150 | $0.01978 |
| Opus 5.5 | $0.00060 | $0.00791 |
| Sonnet 5.5 | $0.00030 | $0.00396 |
| Haiku 4.5 | $0.00015 | $0.00198 |
Grade A, and why
delegate 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 14d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
delegate — coordinate your other Claude Code sessions
Deliver a piece of text from this session to another of your Claude Code
sessions, and drive the delegate/coordinate/monitor loop that a fleet of
tmux-pane or git-worktree agents runs on. Two tools do it: ListAgents
discovers who you can reach; SendMessage delivers one plain-text message
to a peer by name (SendMessage({to: "<name>", message: "..."})).
Full reference: https://code.claude.com/docs/en/cross-session-messaging
When to use this vs. something else
Use messaging when a session that already exists and is being steered separately needs one piece of information from this one, or vice versa:
- Hand over a finding — you changed something that breaks what a peer is building on; warn that peer.
- Coordinate worktrees — tell the other worktrees what landed on the shared repo.
- Pull status — ask a long-running migration/test session to report back.
- Delegate a scoped ask — hand a peer a self-contained unit and collect its reply.
Do not reach for messaging when a purpose-built mechanism fits better:
| Need | Use instead |
|---|---|
| Continue one conversation elsewhere / share its context | resume the session (--resume, /resume) |
| A team of agents THIS session spawns and supervises | subagents (Agent tool) / agent teams |
| Push external events (CI, chat) into a session | channels |
| Steer a session yourself from another device | Remote Control |
A message carries only its text — never conversation history or files. If the peer needs your context, resume it; don't try to narrate the whole session into a message.
Preflight (once per session, when a send fails or peers look missing)
claude --version # need >= 2.1.224 (>= 2.1.232 for @-mention + /config row)
# messaging live iff the socket is bound:
[ -n "$CLAUDE_CODE_MESSAGING_SOCKET" ] && echo "messaging on" || echo "messaging OFF"
If /list-agents isn't recognized, the session predates the feature (v2.1.224).
Same-machine messaging no longer depends on feature-flag fetching, so telemetry
and nonessential-traffic env vars do not turn it off.
What ships with it
1 file 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.
- 14d ago Changed · +4 lines 6b3643f6be22
- 1mo ago First seen · 146 lines · 150 tokens per session scan A aabfa8222fb4
delegate is a skill published in the GitHub repository stefan-jansen/coding-agent-toolkit (33 stars, last pushed yesterday), licensed MIT. It adds 150 tokens to every session and 1,978 once invoked, about $0.0006 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…