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 skillgit 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/skill)<a href="https://agentmods.dev/skills/dentiny/kon/skill"><img src="https://agentmods.dev/badge/skills/dentiny/kon/skill/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/skill"><img src="https://agentmods.dev/badge/skills/dentiny/kon/skill.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.00166 | $0.01243 |
| Opus 5.5 | $0.00066 | $0.00497 |
| Sonnet 5.5 | $0.00033 | $0.00249 |
| Haiku 4.5 | $0.00017 | $0.00124 |
Grade A, and why
kon 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kon — Multi-Agent Workflow
Plugin root (KON_ROOT)
Resolve once at the start of every kon command:
export KON_ROOT="$(python3 "$HOME/.kon/lib/_kon_paths.py" root)"
Resolution order: KON_ROOT env → ~/.kon/config.json → kon clone → ~/Desktop/kon.
All paths below use $KON_ROOT/....
Trigger
When the user invokes a slash command — /kon:team, /kon:design, /kon:quick, /kon:debug, /kon:ask, /kon:review, /kon:review-pr, /kon:hunt, /kon:gc, /kon:research, /kon:describe-issue, /kon:begin, /kon:finish, /kon:summarize, /kon:retro, /kon:address-comments, /kon:todo, /kon:understand-codebase — stop answering directly and run the orchestration flow below.
Orchestration
1. Session file (do this first)
python3 $KON_ROOT/scripts/kon_session.py init --command "/kon:team" --task "…"
2. Read the matching command file
| Command | File |
|---|---|
/kon:team |
$KON_ROOT/commands/team.md |
/kon:design |
$KON_ROOT/commands/design.md + $KON_ROOT/skills/design-debate/SKILL.md |
/kon:quick |
$KON_ROOT/commands/quick.md |
/kon:debug |
$KON_ROOT/commands/debug.md |
/kon:ask |
$KON_ROOT/commands/ask.md |
/kon:review |
$KON_ROOT/commands/review.md |
/kon:review-pr |
$KON_ROOT/commands/review-pr.md |
/kon:hunt |
$KON_ROOT/commands/hunt.md + $KON_ROOT/skills/bug-hunt/SKILL.md |
/kon:gc |
$KON_ROOT/commands/gc.md |
/kon:research |
$KON_ROOT/commands/research.md |
/kon:describe-issue |
$KON_ROOT/commands/describe-issue.md |
/kon:begin |
$KON_ROOT/commands/begin.md + $KON_ROOT/skills/interactive-session/SKILL.md |
/kon:finish / /kon:summarize |
$KON_ROOT/commands/summarize.md |
/kon:retro |
$KON_ROOT/commands/retro.md + $KON_ROOT/skills/session-retro/SKILL.md |
/kon:address-comments |
$KON_ROOT/commands/address-comments.md |
/kon:todo |
$KON_ROOT/commands/todo.md |
/kon:understand-codebase |
$KON_ROOT/commands/understand-codebase.md + $KON_ROOT/skills/understand-codebase/SKILL.md |
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 · 89 lines · 166 tokens per session scan A 3fa8e2cd692d
kon is a skill published in the GitHub repository dentiny/kon (3 stars, last pushed 3mo ago), licensed MIT. It adds 166 tokens to every session and 1,243 once invoked, about $0.0007 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…