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/ximenchuifeng/codex-kimi-bridge/agents-mdgit clone --depth 1 https://github.com/ximenchuifeng/codex-kimi-bridgeWrote 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/ximenchuifeng/codex-kimi-bridge/agents-md)<a href="https://agentmods.dev/instructions/ximenchuifeng/codex-kimi-bridge/agents-md"><img src="https://agentmods.dev/badge/instructions/ximenchuifeng/codex-kimi-bridge/agents-md.svg" alt="Measured on agentmods" 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 | $0.02444 | $0.02444 |
| Opus 5 | $0.01222 | $0.01222 |
| Sonnet 5 | $0.00489 | $0.00489 |
| Haiku 4.5 | $0.00244 | $0.00244 |
Grade B, and why
codex-kimi-bridge AGENTS.md scanned grade B with 1 finding 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 4d 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
Do not commit real tokens. `.mcp.json` keeps `KIMI_SERVER_TOKEN` empty. How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project
codex-kimi-bridge is a local Codex plugin plus MCP bridge. Its purpose is to let Codex act as planner/reviewer while Kimi Code performs implementation through the local Kimi server.
Default workspace:
/Users/ximenchuifeng/Coding/codex-kimi-bridge
Related Kimi Code source checkout:
/Users/ximenchuifeng/Coding/BigWave/kimi-code
Collaboration Rule
The preferred workflow is:
- Codex writes the spec and plan.
- Codex delegates implementation to Kimi through
kimi_delegate_and_wait. - Kimi changes code and runs verification.
- Codex reviews the embedded
reviewPackage, independently verifies, and either accepts or sends follow-up feedback.
Do not manually implement feature work in Codex when the user says execution should happen in Kimi. Codex may still do small local maintenance tasks when explicitly asked, such as reinstalling the plugin, committing already-reviewed work, or writing this file.
Reusable prompt templates live in:
docs/prompts/kimi-delegate-workflow.md
Current Plugin State
Local marketplace:
/Users/ximenchuifeng/Coding/codex-kimi-bridge/.agents/plugins/marketplace.json
Plugin id:
kimi-delegate@codex-kimi-bridge-local
MCP config:
plugins/kimi-delegate/.mcp.json
The plugin MCP server currently launches:
node ./mcp/server.mjs
After code changes that affect MCP tools or plugin config, run:
pnpm build
codex plugin add kimi-delegate@codex-kimi-bridge-local
Then open a new Codex thread or restart Codex if the tool list does not refresh.
plugins/kimi-delegate/mcp/server.mjsis a tracked generated artifact.- Source changes affecting MCP runtime require
pnpm buildand committing the regenerated bundle. - Fresh clone installation does not require pnpm because the bundle is tracked.
- Development reinstalls use
update_plugin_cachebuster.py; release manifests use plain semantic versions.
Kimi Server
Default server:
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.
- 4d ago First seen · 222 lines · 2,444 tokens per session scan B e5c99ff5d53f
codex-kimi-bridge AGENTS.md is an instructions file published in the GitHub repository ximenchuifeng/codex-kimi-bridge (0 stars, last pushed 1mo ago), licensed MIT. It adds 2,444 tokens to every session, about $0.0122 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other instructions, from other repositories
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.
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).
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.
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).