interactive-session

A routing skill for plain-text messages sent during an open coding session. It adds each follow-up to the existing session instead of starting a separate one.

In plain words
What is it for?
Use it when continuing work after a session-start command, including questions, implementation requests, and other messages that do not use a command prefix.
Why use it?
It keeps the conversation and session record together, so follow-up requests do not create duplicate sessions or lose context.

Skill for Claude CodeCodex

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/interactive-session
Any agent
npx skills add dentiny/kon --skill interactive-session
Clone the repo
git clone --depth 1 https://github.com/dentiny/kon

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 924 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.00035 $0.00924
Opus 5 $0.00017 $0.00462
Sonnet 5 $0.00007 $0.00185
Haiku 4.5 $0.00003 $0.00092

Measured yesterday against content hash 6e397dc65483, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

interactive-session 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 yesterday.

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/interactive-session/SKILL.md · 86 lines

How it starts

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

Interactive Session

Owner: orchestrator Consumers: /kon:begin — all follow-up messages without a /kon: prefix

Core principles (always): follow skills/core-principles — first principles (don't hide the issue); simplest, most concise correct solution.

Detect active session

python3 $KON_ROOT/scripts/kon_session.py active
# prints session id, or nothing

Active = most recent command: "/kon:begin" with status in in_progress | waiting for this project.

If active prints an id → user is in interactive mode unless they sent an explicit /kon:* command.

Golden rule

Never call init for sub-turns inside a begin session.

Append work to the existing session:

python3 $KON_ROOT/scripts/kon_session.py log-turn \
  --id <begin-sid> --agent User --summary "<one line paraphrase>"

python3 $KON_ROOT/scripts/kon_session.py complete-agent \
  --id <begin-sid> --agent Azusa --summary "<one sentence>"

Begin sessions stay in_progress after each agent — only /kon:finish closes them.

Intent routing (plain text)

Signal Route Agent(s)
Question about our code / "where is…" / "how does X work" ask 🎸 Azusa read-only
External docs / API / "look up…" research 📚 Jun
Review diff / "check my changes" review 📝 Mio
Review PR / holistic PR check / "review this PR" review-pr 📝 Mio
Summarize issue / GitHub issue thread describe-issue 📚 Jun
Bug / failing test / regression / "X is broken" debug 🎸 Azusa → 🍰 Mugi → User → 🎶 Yui → 🧹 Sawako → 📝 Mio
Small fix, typo, one file quick 🎶 Yui → 📝 Mio
Feature, multi-file, unclear scope team Azusa → pre-plan gate → Mugi → …
Design first, no code yet design Azusa → pre-plan gate → Mugi → debate
Todo / "remind me to…" / add to list todo run kon_todo.py add (no agent)
Greeting / meta / "what can you do" orchestrator no agent spawn — reply + log-turn User

Read the full file on GitHub · 86 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. yesterday First seen · 86 lines · 35 tokens per session scan A 6e397dc65483

Subscribe to this mod's changes

interactive-session is a skill published in the GitHub repository dentiny/kon (3 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 924 once invoked, about $0.0002 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.

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

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens