agentmods.dev

pre-plan-gate

pre-plan-gate is a skill for Claude Code, Codex from dentiny/kon. It costs 56 tokens per session (1,606 once invoked), scanned A, original, MIT.

A required checkpoint that confirms the problem and implementation details are understood before an orchestrator creates a plan for a coding task.

In plain words
What is it for?
Use it before spawning the planning step for /kon:team, /kon:design, or /kon:debug, and to resolve important questions before proposing implementation work.
Why use it?
It prevents planning from being based on guessed requirements or missing constraints. It is used in team, design, and debugging workflows, with limited stated exceptions.

Skill for Claude CodeCodex

not rated 3 1mo ago A scan 56 tokens original MIT
View the source file dentiny/kon
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/dentiny/kon/pre-plan-gate
Any agent
npx skills add dentiny/kon --skill pre-plan-gate
Clone the repo
git clone --depth 1 https://github.com/dentiny/kon

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pre-plan-gate

README.md
[![agentmods](https://agentmods.dev/badge/skills/dentiny/kon/pre-plan-gate.svg)](https://agentmods.dev/skills/dentiny/kon/pre-plan-gate)
Your own site
<a href="https://agentmods.dev/skills/dentiny/kon/pre-plan-gate"><img src="https://agentmods.dev/badge/skills/dentiny/kon/pre-plan-gate.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,606 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00056 $0.01606
Opus 5 $0.00028 $0.00803
Sonnet 5 $0.00011 $0.00321
Haiku 4.5 $0.00006 $0.00161

Measured 3d ago against content hash 61c1e9919691, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pre-plan-gate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pre-plan-gate/SKILL.md · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pre-Plan Gate

Owner: orchestrator Consumers: /kon:team, /kon:design, /kon:debug, and /kon:begin routes that enter those pipelines

Core principles: follow skills/core-principles and skills/ask-dont-guess. Planning without sufficient understanding hides the issue — do not let Mugi write steps that rest on guessed scope, behavior, or constraints.

When this gate runs

Command After Before
/kon:team 🎸 Azusa (+ optional 📚 Jun) 🍰 Mugi plan
/kon:design 🎸 Azusa (+ optional Jun) 🍰 Mugi plan v1
/kon:debug 🎸 Azusa + orchestrator writes debug.md 🍰 Mugi fix proposals

Skip only when:

  • Plan reuse on /kon:team — user chose to reuse an existing plan that already passed this gate (e.g. after /kon:design), and no re-plan.
  • Re-plan after user explicitly chose re-run Azusa + Mugi — gate runs again.

Never skip in --yolo mode. YOLO skips checkpoints inside an approved plan; it does not skip understanding before planning.

Orchestrator workflow

  1. Read inputs (paths only — do not paste bodies into chat):
    • sessions/<SID>/explore.md (team/design)
    • .kon/research.md if present
    • User's original task / bug description
    • For debug: sessions/<SID>/debug.md after Azusa
  2. Summarize Azusa's unknown unknowns — one line each from ## Unknown unknowns (omit if section absent).
  3. Ask the user questions — see Question mix below. Use prose or a short numbered list; use AskUserQuestion only when options are converged.
  4. Wait for answers. Run: 
    python3 $KON_ROOT/scripts/kon_session.py wait-for-user --id "$SID" \
  --after decision --summary "Pre-plan understanding — answer questions before Mugi?"
  5. Evaluate answers. If material gaps remain → ask follow-ups (same gate; do not spawn Mugi). If user says "I don't know" on something that changes the plan → record as open in understanding.md and either ask again with narrower options or stop with "cannot plan until X is known."
  6. Write artifact — sessions/<SID>/understanding.md (template below).
  7. Spawn Mugi with pointer only: 
    UNDERSTANDING_FILE: sessions/<SID>/understanding.md
EXPLORE_FILE: sessions/<SID>/explore.md
PLAN_FILE: …
Read UNDERSTANDING_FILE before planning. Do not replan without addressing every answered question.
  8. After user answers and before Mugi: user-continued --summary "Pre-plan understanding complete".

Read the full file on GitHub · 150 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 150 lines · 56 tokens per session scan A 61c1e9919691

Subscribe to this mod's changes

pre-plan-gate is a skill published in the GitHub repository dentiny/kon (3 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 1,606 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

DebuggingPlanning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens