Download Killer Instinct (zip)
~40 KB · no bundled secrets · pinned lockfile. Two runtime deps fetched on install: @modelcontextprotocol/sdk@^1.12.0, zod@^3.23.8. Sole network egress: your KI brain (call-os.com by default, or your own KI_BRAIN_URL).
SHA-256: 6d11b1ac6a4caaa7171751c277f2707bef8e54e1f7c878257d0093ac98e3d58c
1 · Unzip and install deps
Unzip, then in the mcp folder run npm install --omit=dev to fetch the two pinned runtime dependencies (or use the air-gapped vendored bundle - ask us).
2 · Get your key + register
One command on Windows: setup.ps1 creates your own private, isolated org automatically (or pass -Pin to reuse a key), builds, and registers KI with Claude Code. Unsigned preview - read the script first.
powershell -ExecutionPolicy Bypass -Scope Process -File installer/setup.ps1 -CodeToo
Prefer to do it by hand? Provision a key, then register:
# create your private org -> returns your KI key (save it):
curl -X POST https://call-os.com/tapdeck/api/signup
setx KI_PIN "ki_your-key" # store it; reopen the terminal
claude mcp add killer-instinct -s user \
-e KI_BRAIN_URL=https://call-os.com/tapdeck \
-e KI_PIN=%KI_PIN% \
-- node ./killer-instinct/mcp/dist/index.js
3 · The flywheel is wired for you
setup.ps1 merges two hooks into your ~/.claude/settings.json (backed up first, never clobbered): a guard that screens every shell command, and an auto-instrument that logs a graded episode per commit so the corpus fills itself. Manual form, if you registered by hand:
"PreToolUse": [{ "matcher": "Bash|PowerShell", "hooks": [
{ "type": "command", "command": "node ./killer-instinct/hooks/ki_guard_hook.js" } ]}],
"Stop": [{ "hooks": [
{ "type": "command", "command": "node ./killer-instinct/hooks/ki_episode_hook.js" } ]}]
4 · Restart your session
Claude Code now has the KI tools - ki_recall, ki_boot, ki_check, ki_do, ki_job, ki_learn, ki_record_outcome, ki_simulate, ki_status, ki_start_agent, ki_handoff.
Maintenance & compatibility
KI sits under your workflow, so durability matters: it tracks the MCP standard and the Claude Code hook/settings format, is versioned, and is tested against current Claude Code. It's a single-maintainer developer preview today - an open-source release is planned so adopters aren't exposed to single-maintainer risk. Questions, breakage, or enterprise needs: reach out below.