Borrowing it
Nothing to install: this file belongs to aipper/zentao-mcp. 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/aipper/zentao-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/aipper/zentao-mcpWrote 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/aipper/zentao-mcp/agents-md)<a href="https://agentmods.dev/instructions/aipper/zentao-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/aipper/zentao-mcp/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.1 | $0.00676 | $0.00676 |
| Opus 5 | $0.00338 | $0.00338 |
| Sonnet 5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
zentao-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 5d 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
zentao 协作规则
适用范围：仓库根目录及所有子目录。
目标
- 处理 ZenTao bug 时，优先使用结构化解决说明：
resolve_bug.solutionModules/batch_resolve_my_bugs.solutionModules。 - 模块固定为：
rootCause（根因）、fixApproach（修复思路）、logicChange（改动逻辑）、impact（影响范围）。 - 服务端会把模块格式化为多行文本写入禅道；阅读者应能直接理解“为什么改、改了什么、影响什么”。
bug 回复写法
- 调用 MCP 解决 bug 时，优先传
solutionModules，至少填rootCause+logicChange，完整时四块都写。 - 每块 1 到 3 句，优先业务/产品能理解的改动结果，不堆砌编译、提交、路径等证明信息。
- 如果需要提验证，只写结果型描述，例如“已覆盖空值与重复提交场景”，不要贴命令。
- 不要只写“已修复并自测”这类没有信息量的句子。
- 兼容：仍可传纯文本
solution；若同时传了且solutionModules有任一非空字段，以solutionModules为准。
明确禁止
- 不要把
Evidence:、Verify:这样的模板标签写进 bug 解决说明。 - 不要在 bug 回复里附编译命令、测试命令、文件路径、提交 hash、截图路径。
- 不要把聊天里的通用收尾模板直接复制到 ZenTao 的
solution/solutionModules或comment字段。
工具约定
- 获取 bug 时，优先使用
get_my_bugs。若已知是在项目视角，传projectId（比projectSetId更精确，不会跨项目合并）；若已知是产品视角传productId；若已知是项目集视角传projectSetId，必要时配合path="/my/bug"或环境变量ZENTAO_MY_BUGS_PATH=/my/bug。 get_my_bugs传了projectId后会直接查/projects/{id}/bugs，不再扫描其它项目/产品/项目集路径，实现硬隔离。- 不要默认先依赖
list_my_projects找项目再查 bug；有些项目集没有实际创建项目，也仍然会有“我的 bug”，这类场景可能无法通过项目列表发现。 - 处理 bug 优先填
solutionModules（或兼容字段solution），只有没有合适解决说明时才退回comment。 comment_bug.comment用于补充进展、风险、待验证项，不替代完整的解决说明。- 批量处理时，
solutionModules要写共性根因和共性逻辑调整，不要写单次操作证明。
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.
- 5d ago First seen · 29 lines · 676 tokens per session scan A 46dd80d30fcb
zentao-mcp AGENTS.md is an instructions file published in the GitHub repository aipper/zentao-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 676 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
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).
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).
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.
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.