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/nikolamin/claude-coordinator-kit/bootstrapnpx skills add nikolamin/claude-coordinator-kit --skill bootstrapgit clone --depth 1 https://github.com/nikolamin/claude-coordinator-kitWrote 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/nikolamin/claude-coordinator-kit/bootstrap)<a href="https://agentmods.dev/skills/nikolamin/claude-coordinator-kit/bootstrap"><img src="https://agentmods.dev/badge/skills/nikolamin/claude-coordinator-kit/bootstrap.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.00296 | $0.02450 |
| Opus 5 | $0.00148 | $0.01225 |
| Sonnet 5 | $0.00059 | $0.00490 |
| Haiku 4.5 | $0.00030 | $0.00245 |
Grade A, and why
bootstrap 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 today.
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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap and resume
This skill packages the fresh-install half and the "bootstrap yourself" resume half of
CLAUDE.md's Session stop / resume protocol for delivery via a plugin, and adds the
plugin-specific fresh-install procedure that install replaces: a plugin-based coordinator does not
git-clone the kit and copy PROCESS.md/STATE.md/codex-setup.md into docs/coordination/ the
way the file-copy install's kickoff-prompt.md does. The phase loop and the codex second-opinion
guidance are already on this machine as coordinator-kit:phase-loop and
coordinator-kit:codex-second-opinion, loaded on demand — nothing to copy. The one file this
skill does install is CLAUDE.md itself, from templates/claude-md-spine.md next to this file,
because that one has to physically live in the project root for Claude Code to load it every
session. docs/coordination/STATE.md is also created directly (below) — it is this project's own
live state, not kit content, so there is no template file to copy for it either.
Out of scope for this skill: installing the optional Telegram bridge, seeding
memory-seed/-style memory files, and asking about Chrome browser access. Those are one-time,
optional install choices independent of the plugin's own skills — if this project wants them,
follow the kit's README rather than expecting this skill to drive that interview.
Which path applies: the resume test
Before doing anything else, apply the resume test: this is a resume, not a fresh bootstrap, if
docs/coordination/STATE.md already exists and either its ## Current section reads as anything
other than the single line - Phase: Bootstrap. No tasks dispatched yet., or its ## Agent log
holds any entry beyond one illustrative EXAMPLE entry. A missing or freshly-stubbed STATE.md
reads as a brand-new project; a mature project must never be treated as if none of its work
happened, so check the actual file content, not just whether it exists.
Fresh project: Bootstrap
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.
- today Changed bd3ecc213e41
- 4d ago First seen · 136 lines · 296 tokens per session scan A 0d8cbfd79d67
bootstrap is a skill published in the GitHub repository nikolamin/claude-coordinator-kit (2 stars, last pushed yesterday), licensed MIT. It adds 296 tokens to every session and 2,450 once invoked, about $0.0015 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…