krypton-execution — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited krypton-execution (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Krypton Execution runs an approved plan without drifting from its ownership, cutover, and evidence contract.
Use the role expectations in ../../docs/required-roles.md when the harness supports named agents. Implementation stays with the main agent. The normal execution stack is:
explorer -> main agent -> plan-reviewer -> reviewer -> maintainer -> verifierUse the individual prompt templates in this skill folder:
post-plan-reviewer-prompt.mdreviewer-prompt.mdmaintainer-prompt.mdDo not invent the plan inside this workflow. If no approved plan, goal document, or clear task board exists, ask for one direct input or use Krypton Planning first. Prefer a full Krypton goal package:
docs/goals/<goal-slug>/PLAN.md
docs/goals/<goal-slug>/GOAL.md
docs/goals/<goal-slug>/EVIDENCE.mdBefore work starts, restate:
Goal:
Plan path:
Intent:
Truth owner:
Contract boundary:
Cutover:
Displaced path:
Acceptance evidence:
Kill criteria:
Forbidden moves:Turn the plan into an ordered board:
Task:
Owner:
Input:
Files allowed:
Files forbidden:
Output:
Evidence:
Depends on:
Parallel safe:Run implementation tasks sequentially in the main agent unless the approved plan explicitly says otherwise.
For each task:
The main agent owns implementation, integration, and final coherence.
Do not call the goal complete because tests, lint, typecheck, or diffs passed. Those are supporting checks.
Completion requires target-perspective evidence, such as:
If evidence cannot be captured, report the blocker and say implemented but unproven.
Record the accepted evidence in EVIDENCE.md before the final response when the repo uses Krypton goal packages.
Before final response:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.