kon AGENTS.md

Project instructions for a Python project that explain coding style, formatting, testing, skills, commits, and pushing changes.

In plain words
What is it for?
Use them when editing the project, running its formatter and tests, handling registered skills, or preparing commits and pushes.
Why use it?
They give the coding agent consistent rules for checking code and organizing changes before they are committed or pushed.

Instructions file for CodexOpenCode

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 instructions/0xku/kon/agents-md
Clone the repo
git clone --depth 1 https://github.com/0xku/kon

Made for: Codex, OpenCode.

Per session 305 This file is loaded in full into every session.
When invoked 305 The same file — it is already loaded in full.
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.00305 $0.00305
Opus 5 $0.00152 $0.00152
Sonnet 5 $0.00061 $0.00061
Haiku 4.5 $0.00030 $0.00030

Measured 3d ago against content hash 55ac49e8d82d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

AGENTS.md · 26 lines

What it actually says

Agent Guidelines

Code Style

  • Don't add trivial docstrings. Only add docstrings when explaining complex functionality.
  • This project uses uv. Run uv run ruff format . after editing or creating any files.
  • If generating and running a Python script, use uv run python instead of python.

Testing

  • Use uv run python -m pytest for testing in general; after edits/writes
  • If the user asks for e2e tests then run the kon-tmux e2e test if available

Skills

  • Kon supports registering a skill as a slash command by setting register_cmd: true in the SKILL.md frontmatter. If a user asks for a "registered" skill, include this field.

Committing code

  • If the user tells you to commit code, look at all the changes and create multiple commits if needed based on logical groupings
  • Follow commit message conventions: docs:, feat:, fix:, build:, etc. for the commit prefix

Pushing

  • If the user asks you to push code, run these first before doing so: uv run ruff format ., uv run ruff check ., uv run python -m pyright . and uv run python -m pytest in parallel (same tool call)
  • Only if these all pass without issues should you push otherwise report the warnings/errors back to user and ask for next steps
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. 3d ago First seen · 26 lines · 305 tokens per session scan A 55ac49e8d82d

Subscribe to this mod's changes

kon AGENTS.md is an instructions file published in the GitHub repository 0xku/kon (353 stars, last pushed 1mo ago), licensed MIT. It adds 305 tokens to every session, about $0.0015 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-30.

Related

Other instructions, from other repositories

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens