krypton

Krypton

Current version: 0.3.2

Stop AI agents from shipping plausible wrong work.

Krypton is the goal-based planning and proof gate for running Claude Code, Codex, and other AI coding agents against production-grade codebases.

The failure mode Krypton is built for is not bad syntax. It is the right-looking feature that compiles while living on the wrong layer, inventing a second source of truth, skipping cutover, or claiming success without proof from the real path.

Krypton forces the plan before the code:

• truth owner
• contract boundary
• displaced path
• cutover decision
• acceptance evidence
• review gates

Built for /goals, equivalent goal-based agent workflows, Claude Code skills/plugins, Codex skills, and operators who need agent speed without letting the codebase rot.

What's Included

• New beta: VPS Codex setup (krypton-vps-codex-app): a guided workflow for using a Linux VPS as the remote machine for Codex App work, including VPS readiness questions, SSH aliases, GitHub repo access, local config choices, Codex CLI auth, port forwarding, and proof checks.
• Krypton planning (krypton-planning): turns a request into a goal package with the truth owner, boundary, cutover decision, task plan, review gates, and acceptance evidence.
• Krypton execution (krypton-execution): keeps an approved plan on track while the main agent implements, verifies, and records proof.
• GitHub Action beta: checks pull requests for the goal-package evidence Krypton expects before non-trivial code changes ship.

Jump to: Install | Skills And Beta Workflows | VPS Setup Workflow Beta | GitHub Action Beta

Why Operators Need It

Modern agents can create weeks of architectural debt in one enthusiastic session. Krypton turns "build this" into an operational contract before the agent touches code:

• what product or engineering outcome the work serves
• what current behavior is replaced, redirected, deleted, or demoted
• who owns the truth
• what contract crosses the boundary
• what evidence proves the result from the target person's perspective
• what kill criteria prevent duplicate paths from living forever

That contract is what lets an operator keep using agents on production systems without letting the codebase become a pile of current-looking alternatives.

Designed For /goals

Krypton is best used with /goals or any equivalent goal-based agent workflow. It is not meant to be a one-shot "please implement this" prompt.

The planning session creates the durable handoff:

docs/goals/<goal-slug>/PLAN.md
docs/goals/<goal-slug>/GOAL.md
docs/goals/<goal-slug>/EVIDENCE.md

PLAN.md is the source plan. GOAL.md is the compact /goal prompt. EVIDENCE.md is where execution records the actual proof from the real command, artifact, payload, browser state, trace, or operator-visible result. Start the execution session with the GOAL prompt, then load krypton-execution so the main agent preserves the plan's ownership, cutover, review, and evidence gates.

If your harness does not have /goals, paste the contents of GOAL.md into a fresh Codex or Claude session. The shape still works.

Install

Recommended: skills.sh

Use the open skills CLI when you want Krypton installed into supported agent skill directories:

Codex only:

npx --yes skills add jturntdev/krypton --skill '*' --agent codex --copy -y

Claude Code only:

npx --yes skills add jturntdev/krypton --skill '*' --agent claude-code --copy -y

That installs every Krypton skill for the named agent only. If you want Codex, Claude Code, OpenCode, or another agent together, run the command without --agent ... and use the interactive selector:

npx --yes skills add jturntdev/krypton

See the package page:

https://skills.sh/jturntdev/krypton

Codex Repo Marketplace

This repo ships a Codex marketplace file at .agents/plugins/marketplace.json. For Codex clients that support repo marketplaces:

codex plugin marketplace add \
  "https://github.com/jturntdev/krypton.git" \
  --ref "main" \
  --sparse ".agents/plugins" \
  --sparse ".codex-plugin" \
  --sparse "assets" \
  --sparse "skills"

codex plugin install krypton --source krypton

Claude Code Plugin

Use the plugin route when you want Claude Code to manage Krypton as a plugin:

/plugin marketplace add jturntdev/krypton
/plugin install krypton@krypton-dev
/reload-plugins

Claude Code namespaces plugin skills, so invoke them as:

/krypton:krypton-planning
/krypton:krypton-execution

This repo includes the Claude plugin files Claude Code expects: