Mooncake is a serving platform for Kimi, an LLM service from Moonshot AI, built around sharing and transferring the KV cache used during language-model inference. It supports disaggregated serving and data movement between inference, training, and rollout systems. The catalogue add-ons operate or integrate with Mooncake-based serving and transfer workflows.
Borrowing it
Nothing to install: this file belongs to kvcache-ai/Mooncake. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kvcache-ai/Mooncake/main/AGENTS.mdgit clone --depth 1 https://github.com/kvcache-ai/MooncakeWrote 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/instructions/kvcache-ai/mooncake/agents-md)<a href="https://agentmods.dev/instructions/kvcache-ai/mooncake/agents-md"><img src="https://agentmods.dev/badge/instructions/kvcache-ai/mooncake/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.
<a href="https://agentmods.dev/instructions/kvcache-ai/mooncake/agents-md"><img src="https://agentmods.dev/badge/instructions/kvcache-ai/mooncake/agents-md.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.00315 | $0.00315 |
| Opus 5.5 | $0.00126 | $0.00126 |
| Sonnet 5.5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
Mooncake 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 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.
What it actually says
AGENTS.md
docs/ Directory Changes
- Before modifying files under
docs/, readdocs/AGENTS.md.
Pull Request Guidelines
- Follow
CONTRIBUTING.mdfor PR title prefixes, RFC expectations, and contribution workflow. - Before opening a PR for nontrivial work, check whether an existing issue or open PR already covers the same change. If the work overlaps, explain the difference instead of duplicating it.
- Do not open low-value busywork PRs for isolated typo, style, or mechanical changes unless they are part of a substantive requested change.
- Use
.github/pull_request_template.mdwhen preparing a PR, and fill in the relevant sections for description, module, type of change, testing, checklist, and AI assistance disclosure. - For AI-assisted changes, make sure the human submitter has reviewed every changed line and can defend the change end-to-end.
- Before handoff, run pre-commit on the files touched by the change when the
toolchain is available (see
CONTRIBUTING.mdfor the PR-scopedpre-commit run --files ...command). Do not usepre-commit run --all-filesfor routine PRs; if it rewrites unrelated files, leave those edits out of the PR. - Keep PRs lean: review
git diffbefore staging, and include only changes required for the requested task.
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 · 28 lines · 315 tokens per session scan A ea1d953b4e45
Mooncake AGENTS.md is an instructions file published in the GitHub repository kvcache-ai/Mooncake (6,818 stars, last pushed yesterday), licensed Apache-2.0. It adds 315 tokens to every session, about $0.0013 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-30.
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).
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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).