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/lemon07r/opencode-kimi-full/agents-mdgit clone --depth 1 https://github.com/lemon07r/opencode-kimi-fullWhat 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.04096 | $0.04096 |
| Opus 5 | $0.02048 | $0.02048 |
| Sonnet 5 | $0.00819 | $0.00819 |
| Haiku 4.5 | $0.00410 | $0.00410 |
Grade A, and why
opencode-kimi-full 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — working notes for coding agents (and humans)
This file is the single source of truth for any AI agent (or human) modifying this repo. Read it top-to-bottom before touching code. If something you learn here contradicts what you see in the code, the code wins — update this file in the same commit.
User-facing install / usage documentation lives in README.md. Do not duplicate it here.
Purpose
One plugin, one job: make opencode talk to Kimi's kimi-for-coding endpoint exactly the way the official kimi-cli does. Everything in this repo exists to minimize drift from upstream kimi-cli.
The one rule that matters
Moonshot's coding backend is entitlement-sensitive: the model-name string alone is not the whole story.
Every design decision here follows from that: we do device-flow OAuth to mirror official kimi-cli, we do not accept API keys in this plugin, and we do not let the upstream SDK attach its own Authorization header.
Non-goals
- No support for any non-
kimi-for-codingmodel. opencode already handles other Moonshot / Baseten / Alibaba-CN / etc. entries itself. - No support for static API keys. Users who want that can use a different opencode provider entry.
- No custom SSE parser, tool-call normalizer, or message rewriter.
@ai-sdk/openai-compatiblealready does SSE/reasoning_contentcorrectly.
Architecture
Each source file has one job. Do not add new files unless the existing ones genuinely can't hold a new concern.
| File | Responsibility |
|---|---|
src/constants.ts |
Pinned strings that must mirror upstream kimi-cli (version, endpoints, client id). |
src/headers.ts |
The seven X-Msh-* / UA headers + the persistent ~/.kimi/device_id file. |
src/oauth.ts |
Device-code start, device-code poll, refresh-token exchange, and GET /coding/v1/models discovery. |
src/auth-store.ts |
Read/write opencode's auth.json entries for this provider. |
src/auth-refresh.ts |
Lock-based token refresh with cross-instance coordination, ensureFreshStoredAuth for standalone callers. |
src/index.ts |
Plugin entry (v1 PluginModule format). Wires auth (login + loader) plus the Kimi chat hooks/body rewrite. |
src/usage.ts |
Fetch and parse Kimi subscription usage (/coding/v1/usages). |
src/tui.tsx |
TUI slash command /kimi:usage — renders usage in an opencode dialog. |
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 · 129 lines · 4,096 tokens per session scan A 965cc54784bb
opencode-kimi-full AGENTS.md is an instructions file published in the GitHub repository lemon07r/opencode-kimi-full (121 stars, last pushed 3mo ago), licensed MIT. It adds 4,096 tokens to every session, about $0.0205 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.
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.
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).
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.
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.