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/htmambo/coding-bridge-mcp/agents-mdgit clone --depth 1 https://github.com/htmambo/coding-bridge-mcpWhat 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.00671 | $0.00671 |
| Opus 5 | $0.00336 | $0.00336 |
| Sonnet 5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
coding-bridge-mcp 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 yesterday.
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
Coding Bridge MCP 自动审查规范
本项目已接入 coding-bridge MCP Server（火山方舟 / 讯飞 Coding Plan）。你必须在以下节点主动调用对应的 MCP 工具，并把审查结论纳入最终回复。
1. 计划审查（形成思路后）
在形成初步实现思路、但尚未开始编码前，调用：
mcp__coding-bridge__review_plan- 参数：
PLAN：当前实现计划或方案文本cd：当前项目根目录CONTEXT：项目背景、约束、目标（可选但推荐）SESSION_ID：空字符串开始新会话；如需追问则沿用返回的 IDmodel：模型版本（可选，留空用 provider 默认模型）return_all_messages：返回完整消息历史（可选，默认 false，调试用）
2. 代码审查（完成修改后）
每次对 src/、tests/ 或配置文件做出实质性修改后，必须调用：
mcp__coding-bridge__review_code- 参数：
CODE：需要审查的完整代码或 diff。优先传入完整相关函数/类，确保上下文完整。cd：当前项目根目录REQUIREMENTS：额外上下文，例如修改原因、边界情况、需要重点关注的点SESSION_ID：空字符串开始新会话；如需追问则沿用返回的 IDmodel：模型版本（可选，留空用 provider 默认模型）return_all_messages：返回完整消息历史（可选，默认 false，调试用）
3. 多轮追问（保存 SESSION_ID）
每次调用 review_plan / review_code / chat 后，返回中都会包含 SESSION_ID。必须保存该 ID，以便对同一话题继续追问，保持上下文连续。
4. 判断原则
Coding Plan / 星火返回的审查结论仅供参考。你仍需保持独立判断，不盲从；对于明显不合理的建议，应在最终回复中说明原因。
5. 何时必须审查
- 新增功能、修复 bug、重构代码之后
- 修改核心配置（如
pyproject.toml、Provider 默认值、API 客户端）之后 - 在最终向用户汇报“已完成”之前，确认已执行 review
6. 工具列表速查
mcp__coding-bridge__chat— 通用多轮对话mcp__coding-bridge__review_code— 代码审查mcp__coding-bridge__review_plan— 计划/方案审查mcp__coding-bridge__get_token_stats— 查询当前累计 token 用量
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.
- yesterday First seen · 51 lines · 671 tokens per session scan A 3227342a28c2
coding-bridge-mcp AGENTS.md is an instructions file published in the GitHub repository htmambo/coding-bridge-mcp (0 stars, last pushed 8d ago), licensed MIT. It adds 671 tokens to every session, about $0.0034 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-31.
Other instructions, from other repositories
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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
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.