the integrations
Codex
Codex installs the identical plugin kit from the identical repo — skills, subagents, commands, the MCP oracle. Source, license and claims live in the repo — this room is its projection, never its replacement.
- clientthe kindplug it into your tool
- MITthe licenseread it in the repo
- 3install stepsthe ritual below
- 2of 14prev / next walk them
how it works
One marketplace, every client: the kit is authored once and served to Claude Code and Codex from the same source, so the delegation idiom never forks. The agent drafts the workflow, `nika check` audits it before anything runs, the trace verifies after.
get set up
- 1Add the marketplace
codex plugin marketplace add supernovae-st/nika-agents - 2Install the kit
codex plugin add nika@nika - 3Upgrade later
codex plugin marketplace upgrade nika
Running Claude Code as well? Same marketplace, same two commands. Nika for Claude Code →
what lands in the agent
4 skills · 3 subagents · 5 commands · 9 oracle toolsthe skills · when to reach for nika
- nika-authoring
- nika-debugging
- nika-operating
- nika-migration
the subagents · author, debug, migrate
- nika-author
- nika-debugger
- nika-migrator
the commands · one keystroke each
- /nika:check
- /nika:explain
- /nika:new
- /nika:trace
- /nika:permits
the oracle tools · read-only, one room each
cross-references
the rooms it touches
where it lives
Start local: install. The whole language lives in the map. Read the spec →