Krypton Execution

What it does

When your agent uses it

• Executing an approved Krypton plan
• Implementation plan that already defines intent
• Task boundaries
• Acceptance evidence

Example prompts

• “/krypton-execution”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

1. 1Confirm the task still matches the plan contract.
2. 2Gather only the context needed for the task.
3. 3Implement directly in the main agent.
4. 4Review the result before integration or checkpoint.
5. 5Check for wrong owner, duplicate path, missing cutover, contract drift, and weak proof.
6. 6Commit or checkpoint only the current task files when the local workflow expects commits.
7. 7Update the task board.

What it can do on your machine

Read from SKILL.md and the folder at commit 0b95d97. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md.

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Krypton Execution loads about 841 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 368 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~74

When it runs · the whole SKILL.md, loaded when a task matches

~841

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jturntdev/krypton at commit 0b95d97, republished under its MIT licence (© jturntdev). 368 words, ~841 tokens.

name

krypton-execution

description

Use when executing an approved Krypton plan, GOAL.md, or implementation plan that already defines intent, ownership, contract, cutover, task boundaries, and acceptance evidence. Use for main-agent execution with explorer, plan-reviewer, reviewer, maintainer, or verifier gates.

explorer -> main agent -> plan-reviewer -> reviewer -> maintainer -> verifier

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

Goal:
Plan path:
Intent:
Truth owner:
Contract boundary:
Cutover:
Displaced path:
Acceptance evidence:
Kill criteria:
Forbidden moves:

Task:
Owner:
Input:
Files allowed:
Files forbidden:
Output:
Evidence:
Depends on:
Parallel safe:

© jturntdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files in skills/krypton-execution of jturntdev/krypton.

• SKILL.md
• agents/openai.yaml
• maintainer-prompt.md
• post-plan-reviewer-prompt.md
• reviewer-prompt.md

Open the folder on GitHubat commit 0b95d97

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jturntdev/krypton, which our catalogue first saw on October 7, 2026.

• hashgraph-online/awesome-codex-pluginsplugins/jturntdev/krypton/skills/krypton-execution