taylorsalmon

Kamino — Development skill for Claude Code

Development community

Kamino: the Star Wars ocean world where the clone army is grown, trained, and commanded.

How to install Kamino

This entry records only its repository, not the path inside it, so there is no exact command to give. Open taylorsalmon/kamino and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Kamino does

Kamino: the Star Wars ocean world where the clone army is grown, trained, and commanded. This one grows Claude Code agents instead — agent orchestration with live status, embedded terminals, and command of every Claude instance on the machine, so you never lose track of what each agent is working on.

Alternatives in Development

  • North Star Metric — Define North Star Metric and input metrics constellation 7.8k ★
  • GenericAgent — Self-evolving agent: grows skill tree from 3.3K-line seed, achieving full system control with 6x less token co 6.1k ★
  • Om Weekly — Weekly synthesis — cross-session review of vault activity, North Star alignment, patterns, uncaptured wins, an 4.6k ★

README

KAMINO

**Grow the clones. Command the fleet.**

*Agent orchestration for coding CLIs — Claude Code, Codex, or your own — one window, every instance on the machine, live.*


In Star Wars, Kamino is the storm-wracked ocean world where the clone army is grown, trained, and commanded from a single facility. This Kamino grows coding agents instead — Claude Code and Codex out of the box, any other CLI you add — and since every instance is literally a clone of the same model, the name fit too well to pass up.

When you run multiple coding agents at once, the hard part isn't starting them — it's remembering what each one is doing. Which one is mid-task? Which one asked you a question twenty minutes ago and has been sitting blocked ever since? What did the one in that other terminal actually ship? Past two or three instances, that state stops fitting in your head.

Kamino is the answer: one window that discovers **every** Claude Code instance on the machine (its own embedded terminals, other terminal windows, headless background sessions), and for each one shows live what it's working on — current activity line, evolving task title, repo + branch, PRs opened, queued prompts — and flags the moment one needs your input (Windows toast included). It's mission control for an agent workforce, so your working memory doesn't have to be.

You say Kamino says
launch an instance commission a clone
embedded in the app in bay
running in another terminal field-deployed
headless / background covert ops
kill an instance decommission
kill every clone on the board Order 66

Run it

Installed app (the normal way — survives terminal closes, auto-starts at login):

npm install
npm run package        # → release/Claude Fleet Setup .exe

Run the setup exe (per-user, no admin). It installs to `%LOCALAPPDATA%\Programs\kamino`, registers auto-start at login (`HKCU\...\R