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 instructions/dentiny/kon/agents-mdgit 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.00766 | $0.00766 |
| Opus 5 | $0.00383 | $0.00383 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
kon AGENTS.md 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 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.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kon contributor instructions for AI agents
Hard rules (apply to every agent, every command)
- Never run
git commitorgit push. Draft commit messages and present them to the user. The user runs the command themselves. - Ask, don't guess. If anything material is unclear at any stage (plan, debug, review, impl, …), ask the user before proceeding — never invent facts, behavior, or fixes. See
skills/ask-dont-guess. - Agents may run
git status,git diff,git log,git add— read-only and staging operations are fine.
Core principles (design → impl → review)
Every agent and skill follows skills/core-principles:
- First principles — don't hide the issue — restate the actual problem; every piece must trace back to it. Unclear intent or missing evidence → ask or stop — never assume or paper over.
- Simplest, most concise correct solution — among all correct approaches, choose the minimum that satisfies acceptance criteria; simplicity wins ties.
Tone
This project is emoji-friendly. When working in this repository (including meta-discussion about kon's own design — skills, commands, agents), default to allowing emoji use where it aids clarity or matches the project's voice:
- Agent identity markers — 🎸 Azusa / 📚 Jun / 🍰 Mugi / 🎶 Yui / 📝 Mio / 🧹 Sawako / 📋 Nodoka
- Narrator marker — 🌸 Ui
- Section / status markers in chat output where they aid scanning
The global "avoid emojis unless asked" default does not apply here — that default is overridden for this repository.
Agent & narrator emoji — quick-ref (always in context)
Every mention of an agent or narrator name in prose, summaries, and chat output must carry the emoji prefix — not just the line where they speak.
| Role | Emoji | Name |
|---|---|---|
| Explorer | 🎸 | Azusa |
| Researcher | 📚 | Jun |
| Planner | 🍰 | Mugi |
| Implementer | 🎶 | Yui |
| Reviewer | 📝 | Mio |
| Cleaner | 🧹 | Sawako |
| Summarizer | 📋 | Nodoka |
| Narrator | 🌸 | Ui |
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 · 67 lines · 766 tokens per session scan A 02c4b6a89d59
kon AGENTS.md is an instructions file published in the GitHub repository dentiny/kon (3 stars, last pushed 1mo ago), licensed MIT. It adds 766 tokens to every session, about $0.0038 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.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.