Installation

Kiyo is distributed as static plugin packages. The host installs the package; Kiyo has no installer, generator, or runtime of its own. Each route below shows its evidence status, so you can see which steps have been exercised.

Before you install

• Prepared packages only. Install one of the generated packages in dist/, never the unbuilt src/kiyo/ tree or the repository root as a raw plugin source. The root catalog files point to ./dist/... for this reason.
• Repository path. The GitHub repository is now 0xPratyaDev7x/kiyo-axiom-framework. The framework README at the documented revision still shows the previous path 0xPratyaDev7x/kiyo-codejadee-framework, which GitHub redirects. Commands on this site use the current path.
• Development identity. The plugin ID is kiyo-axiom-framework and the catalog name is kiyo-codejadee. Neither is a reserved, final release identity, and the product version is UNSET.
• Host policy wins. If your organization or host denies a plugin source or capability, resolve it with the administrator. Do not use bypass flags or broaden permissions.
• Windows is the observed platform. Recorded checks ran on Windows 10.0.26200 with PowerShell. Commands are identical on macOS and Linux shells unless noted, but those systems have no recorded Kiyo evidence.

Packages and archives

Ecosystem	Package root in the repository	Development ZIP	Files
Claude Code	dist/claude/	kiyo-axiom-framework-claude-development.zip	794
Codex	dist/codex/kiyo-axiom-framework/	kiyo-axiom-framework-codex-development.zip	795
GitHub Copilot	dist/copilot/kiyo-axiom-framework/	kiyo-axiom-framework-copilot-development.zip	794

Each ZIP has a single kiyo-axiom-framework/ root folder. Extract the whole archive; installing only SKILL.md files leaves the Skills without their references.

Install by host

Claude Code CLI

Catalog route (from the README; NOT_TESTED). The repository root contains a custom Claude marketplace file, .claude-plugin/marketplace.json, whose plugin source is ./dist/claude.

Claude Code session

/plugin marketplace add 0xPratyaDev7x/kiyo-axiom-framework
/plugin install kiyo-axiom-framework@kiyo-codejadee

Session-only local trial (documented; flag behavior DOCUMENTED_ONLY). Extract the Claude ZIP to a folder of your choice, open your project, and pass the extracted root:

PowerShell

claude --plugin-dir "C:\path\to\extracted\kiyo-axiom-framework"

This loads the plugin only for that session and does not install it globally. The framework records that claude --plugin-dir <root> plugin details kiyo-axiom-framework enumerated all eight Skills from both a directory and a ZIP on Claude Code 2.1.220 (VERIFIED for discovery only, recorded under the earlier plugin ID kiyo-compass).

Validation note. claude plugin validate <root> exits 0 with warnings about the missing version and author. claude plugin validate --strict fails (FAIL) for the same reason, because those owner fields are intentionally unset.

Claude Code VS Code

Use the Claude panel: type /plugins, then use the Plugins and Marketplaces tabs with an approved marketplace or source, and pick user, project, or local scope. The route is DOCUMENTED_ONLY; Kiyo installation in the extension is NOT_TESTED.

The Claude documentation lists VS Code 1.94.0 or later and a paid Claude plan or Console account as requirements for the extension. Results from the CLI are not evidence for the extension.

Codex CLI

Catalog route (from the README; NOT_TESTED). The Codex catalog is .agents/plugins/marketplace.json, pointing to ./dist/codex/kiyo-axiom-framework.

PowerShell

codex plugin marketplace add 0xPratyaDev7x/kiyo-axiom-framework
codex plugin add kiyo-axiom-framework@kiyo-codejadee

Local catalog route. Register an approved local catalog, install the plugin by its actual ID, then start a new session:

PowerShell

codex plugin marketplace add "<approved local catalog root>" --json
codex plugin add "<actual plugin>@<actual catalog>" --json

A disposable local-catalog install, cache, and uninstall was VERIFIED on Codex CLI 0.158.0. The native cache matched the distribution byte for byte, and uninstall left project files untouched. The test used a synthetic catalog name and the earlier plugin ID kiyo-compass. Catalog registration changes native configuration, so use a disposable environment for trials. The exact commands are in the framework’s reproduction guide.

Codex reports version 1.0.0 for the installed plugin. That is a host fallback because the manifest has no version, not a Kiyo release.

Codex IDE

Not supported. Official OpenAI documentation excludes plugins from the IDE extension (UNSUPPORTED). Standalone Skills are a different mechanism, and no Kiyo fallback has been approved. This is owner decision DEC-004, still open. Do not copy Kiyo Skills into a global directory as a workaround.

Copilot CLI

Catalog route (from the README; NOT_TESTED). The Copilot catalog is .github/plugin/marketplace.json, pointing to ./dist/copilot/kiyo-axiom-framework.

PowerShell

copilot plugin marketplace add 0xPratyaDev7x/kiyo-axiom-framework
copilot plugin install kiyo-axiom-framework@kiyo-codejadee

Direct directory route (DOCUMENTED_ONLY):

PowerShell

copilot plugin install "C:\path\to\extracted\kiyo-axiom-framework"

Review the native install scope before running it. Copilot plugin storage can be user-scoped, so this is not a guaranteed project-only install. The framework’s Copilot notes record these requirements: a Copilot plan, your organization’s CLI policy, PowerShell 6 or later on Windows, and Node.js 22 or later for the npm-based CLI install.

Copilot VS Code

Use the Agent Plugins experience: search @agentPlugins in Extensions, use the Plugins tab in Chat: Open Customizations, or run Chat: Install Plugin From Source with an approved Git source. For a local trial you can add the extracted package to the chat.pluginLocations setting. That is an explicit settings change, and Init never makes it for you. The chat.plugins.enabled setting must be on. This route is DOCUMENTED_ONLY and NOT_TESTED. Kiyo is an agent plugin, not a VSIX extension.

Verify the installation

1. Open the host’s plugin or Skill list and confirm the source is Kiyo (kiyo-axiom-framework), not a built-in command.
2. Confirm all eight entries are present: init, requirement, implement, review, test, security, architecture, memory.
3. Select Init and ask for a preview. If the agent reports missing references/kiyo/ files, the package was installed incompletely. Reinstall from a complete package.
4. Optionally, select Security and ask for a self-check: “Report exposed Kiyo identity, readable resources and activation evidence.” This reports what the host actually exposes. It does not certify integrity or isolation.

What installation does not do

• It does not load the Core into every session. Explicit selection is the reliable route. See Activation and loading.
• It does not create .kiyo/ files or edit CLAUDE.md, AGENTS.md, or Copilot instructions. Only an explicitly authorized Init does that.
• It does not change host permissions. Kiyo’s access contracts are advisory.

For update and removal, see Update, uninstall, project state. Exact commands for every host are collected in Host commands and selectors.