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.
npx skills add dentiny/kon --skill interactive-sessiongit clone --depth 1 https://github.com/dentiny/konWrote 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.
[](https://agentmods.dev/skills/dentiny/kon/interactive-session)<a href="https://agentmods.dev/skills/dentiny/kon/interactive-session"><img src="https://agentmods.dev/badge/skills/dentiny/kon/interactive-session/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dentiny/kon/interactive-session"><img src="https://agentmods.dev/badge/skills/dentiny/kon/interactive-session.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.00924 |
| Opus 5.5 | $0.00014 | $0.00370 |
| Sonnet 5.5 | $0.00007 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00092 |
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 1mo 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.
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 |
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.
- 1mo ago First seen · 86 lines · 35 tokens per session scan A 6e397dc65483
interactive-session is a skill published in the GitHub repository dentiny/kon (3 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 924 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…