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 agentmods add skills/dentiny/kon/session-trackingnpx skills add dentiny/kon --skill session-trackinggit clone --depth 1 https://github.com/dentiny/konWhat 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 | $0.00047 | $0.03590 |
| Opus 5 | $0.00023 | $0.01795 |
| Sonnet 5 | $0.00009 | $0.00718 |
| Haiku 4.5 | $0.00005 | $0.00359 |
Grade A, and why
session-tracking scanned grade A with 1 finding 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 2d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
root = pathlib.Path(subprocess.check_output(['python3', str(bundled), 'root'], text=True).strip()) How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Tracking
Owner: orchestrator
Consumers: all /kon:* commands (including /kon:ask)
Core principles (always): follow skills/core-principles — record session state accurately; don't hide blocked or failed stages.
The orchestrator writes and updates a session file so scripts/dashboard.py
can display live status and a clickable log of every run.
Session directory layout
Each run gets one directory — delete the folder (dashboard 🗑) and all artifacts go with it:
~/.kon/projects/<repo-name>/sessions/<session-id>/
session.json # status, log, pipeline steps
summary.md # Nodoka debrief (optional)
plan.md # Mugi plan
explore.md # Azusa exploration (/kon:team, /kon:design)
understanding.md # Pre-plan Q&A (team, design, debug — orchestrator)
review.md # Mio review (team, quick, review, debug)
pr-review.md # Mio holistic PR review (/kon:review-pr)
issue-summary.md # Jun issue summary (/kon:describe-issue)
hunt.md # Azusa bug hunt (/kon:hunt)
debug.md # Azusa/Mugi debug notes (/kon:debug)
design-debate.md # design debate (/kon:design)
review-rubric.md # Mugi rubric (/kon:review --rubric)
Resolve paths from the orchestrator:
SID=$(python3 $KON_ROOT/scripts/kon_session.py init --command "/kon:team" --task "...")
SESSION_DIR=$(python3 $KON_ROOT/scripts/kon_session.py session-dir --id "$SID")
PLAN_FILE=$(python3 $KON_ROOT/scripts/kon_session.py artifact-path --id "$SID" --name plan.md)
Pass PLAN_FILE, SESSION_DIR, etc. in Task prompts. Legacy flat files (.kon/plan-<id>.md, sessions/<id>.json) are still removed on delete if present.
Session file location
~/.kon/projects/<repo-name>/sessions/<session-id>/session.json (override root with KON_DATA_DIR)
<repo-name> is the git repo root directory name (e.g. kon for ~/Desktop/kon).
Created automatically on Cursor session start via ensure_project_dir hook (creates the directory only).
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.
- 2d ago First seen · 291 lines · 47 tokens per session scan A a996c4bae284
session-tracking is a skill published in the GitHub repository dentiny/kon (3 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 3,590 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.