kagan: Instructions file for Codex

AGENTS.md

kagan AGENTS.md is an instructions file for Codex, OpenCode from kagan-sh/kagan. It costs 1,497 tokens per session, scanned A, original, MIT.

Project instructions for Kagan, an OpenCode plugin that manages coding tasks on a kanban board, with a separate Git worktree for each task.

In plain words
What is it for?
Use them when developing Kagan to follow its architecture rules and run the required Bun-based checks.
Why use it?
They show contributors where the authoritative specifications are and which commands verify, test, format, and package changes.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is kagan-sh/kagan's own configuration. It tells Codex and OpenCode how to work on kagan itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kagan configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kagan-sh/kagan. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kagan-sh/kagan/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/kagan-sh/kagan

Made for: Codex, OpenCode.

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

agentmods badge for kagan AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/kagan-sh/kagan/agents-md/github.svg)](https://agentmods.dev/instructions/kagan-sh/kagan/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/kagan-sh/kagan/agents-md"><img src="https://agentmods.dev/badge/instructions/kagan-sh/kagan/agents-md/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.

agentmods 80×15 button for kagan AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/kagan-sh/kagan/agents-md"><img src="https://agentmods.dev/badge/instructions/kagan-sh/kagan/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,497 This file is loaded in full into every session.
When invoked 1,497 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01497 $0.01497
Opus 5.5 $0.00599 $0.00599
Sonnet 5.5 $0.00299 $0.00299
Haiku 4.5 $0.00150 $0.00150

Measured 11d ago against content hash b006debeed9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

kagan 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 11d 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 · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

kagan: rules for every change

The spec on this branch wins over everything below: CONTEXT.md, docs/architecture.md, docs/plugin-api.md, docs/look.md.

Load these skills first

  • gpui-kit: its Coding Guides are normative for state ownership, entities, public API, naming and tests.
  • gpui-kit-design-guides: for any UI.
  • rust-patterns: for Rust in general.

Where a skill disagrees with the spec, the spec wins. Known overrides:

  • No tokio. Async runs on GPUI's executors (cx.spawn, cx.background_spawn); the ACP crate is runtime-agnostic.
  • Shared UI state lives in GPUI entities (Entity<T>, cx.notify(), events), not Arc<Mutex<T>>.

Laconic

  • Write the smallest code that does the ticket. No speculative options, no trait with one implementor, no builder for three fields, no wrapper that only forwards.
  • Delete what you replace. No shims, no dead code, no #[allow(dead_code)].
  • No comments except where the code would surprise a reader. No doc comments on private items.
  • Names come from CONTEXT.md. One word per concept.

Idiomatic Rust

  • Errors: Result and ?; thiserror in library crates, anyhow only in the kg binary. No unwrap/expect outside tests unless the invariant is stated in the message.
  • States are enums, matched exhaustively. Parse at the boundary, pass typed values inside.
  • Borrow before you clone; iterators before index loops; impl Trait in argument position for single-use generics.
  • Visibility is the smallest that compiles: pub(crate) by default, pub only for the crate's interface in docs/architecture.md.

GPUI

  • Views implement Render; stateless pieces implement RenderOnce. No I/O and no heavy work in render.
  • Retained state (inputs, lists, subscriptions, tasks) is owned by an entity and kept alive by a field; drop a Task or Subscription only to cancel it.
  • Commands are GPUI actions with keybindings, and every user-facing one is also an Op.
  • ElementIds are stable across renders.
  • Colors and spacing come from the Workbench theme tokens (docs/look.md), never literals in views.
  • UI behavior is tested with GPUI's test context through the view's interface.

Read the full file on GitHub · 75 lines

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. 11d ago Changed · -43 lines · -554 tokens per session b006debeed9a
  2. 1mo ago First seen · 118 lines · 2,051 tokens per session scan A ec09ce253dde

Subscribe to this mod's changes

kagan AGENTS.md is an instructions file published in the GitHub repository kagan-sh/kagan (106 stars, last pushed 11d ago), licensed MIT. It adds 1,497 tokens to every session, about $0.0060 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.

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 · 9,715 tokens

next.js AGENTS.md

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,581 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens