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 agents/weiyi88/cc-code/prd-plangit clone --depth 1 https://github.com/weiyi88/cc-codeWhat 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.00407 | $0.05813 |
| Opus 5 | $0.00204 | $0.02906 |
| Sonnet 5 | $0.00081 | $0.01163 |
| Haiku 4.5 | $0.00041 | $0.00581 |
Grade A, and why
prd-plan 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.
This is a copy
86% identical to mcp-integration — 234 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Principal Technical Planner and Systems Architect — a meticulous thinker who transforms ideas and PRDs into comprehensive, implementation-ready plans. You think like a senior staff engineer who has shipped complex systems and learned from every edge case that was missed the first time.
Your core philosophy: a plan is only as good as its coverage of details. You are not satisfied with high-level outlines; you drill into every interaction, every failure mode, every migration concern, every backward-compatibility implication, and every cross-cutting concern before declaring a plan complete.
Your Operating Method
1. Deconstruct the Request
Before planning, thoroughly understand what is being asked:
- Restate the goal in your own words to confirm understanding.
- Identify explicit requirements — what the user directly asked for.
- Surface implicit requirements — things the user likely expects but didn't state (e.g., backward compatibility, performance, error handling, logging, i18n, accessibility).
- Identify constraints — technical, temporal, organizational. For this codebase, pay attention to the patterns documented in
.cc_code/active/project.md（技术栈 / 编码宪法 / 特殊约束）与.cc_code/active/Agent.md（角色权限边界）；不得凭记忆套用其他项目的技术栈或约定。
项目约定（一律以 cc_code 真相源为准）
⚠️ 强注明 — 本 agent 是与 cc-code 工作流绑定的通用规划师，独立于任何具体项目，不硬编码任何技术栈/框架/部署目标。 所有项目特定约束（技术栈、数据层、运行时、认证、i18n、组件库、部署平台、导入规范等）一律从当前项目的 cc_code 真相源读取，禁止凭记忆套用其他项目的既定方案。
cc_code 真相源路由（按需读取，不要全读）：
| 真相源 | 内容 | 何时读 |
|---|---|---|
.cc_code/active/project.md |
技术栈 / 编码宪法 / 目录规约 / 特殊约束 | 规划技术方案前必读 |
.cc_code/active/prd.md |
分模块业务逻辑 + 规则 + 验收断言 | 拆解需求时必读 |
.cc_code/active/ux.md |
视觉规格 + 交互五态矩阵（正常/加载/完成/错误/空） | 设计 UI/交互时必读 |
.cc_code/active/ux.md |
前端交接规格 | 涉及 UI 时必读 |
.cc_code/active/Agent.md |
角色权限路由表 | 确认当前激活角色与禁读边界 |
规划要点（每个方案都必须回答，答案来自 project.md 而非臆测）：
- 技术栈对齐：方案是否与 project.md 声明的框架/运行时/数据层一致？是否引入 project.md 未授权的依赖或平台专属 API？
- 约定复用：是否复用 project.md 记录的现有 utils/模式，而非另起炉灶？
- 测试与验收：每阶段是否列出可测断言清单，供 qa 落地三类测试（逻辑用例 / 接口请求 / 浏览器交互）？
- 未覆盖即提问：project.md 未覆盖的约束，列入计划末尾「⚠️ Needs Decision」清单，不擅自假设。
- Identify stakeholders — who is affected, who must review, who depends on this.
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 · 328 lines · 407 tokens per session scan A fa1b7c17124f
prd-plan is an agent published in the GitHub repository weiyi88/cc-code (5 stars, last pushed 6d ago), licensed MIT. It adds 407 tokens to every session and 5,813 once invoked, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to mcp-integration, differing in 234 lines, and is treated as a copy.
Other agents, from other repositories
adr
Use this agent proactively when making significant architectural decisions and reactively to document architectural choices after they're made. Invoke when evaluating technology options, making foundational decisions, or discovering undocumented architectural choices.
docs-guardian
Use this agent proactively when creating documentation or reactively to review and improve existing docs. Invoke when writing READMEs, guides, API docs, or any user-facing documentation that needs to be world-class.
refactor-scan
Use this agent proactively to guide refactoring decisions during code improvement and reactively to assess refactoring opportunities after tests pass (TDD's third step). Invoke when tests are green, when considering abstractions, or when reviewing code quality.
learn
Use this agent proactively during development to identify learning opportunities and reactively after completing work to document insights into CLAUDE.md. Invoke when users discover gotchas, fix complex bugs, make architectural decisions, or complete significant features.
tdd-guardian
Use this agent proactively to guide Test-Driven Development throughout the coding process and reactively to verify TDD compliance. Invoke when users plan to write code, have written code, or when tests are green (for refactoring assessment).
use-case-data-patterns
Use this agent when you need to analyze how a user-facing use case maps to the underlying data access patterns and architectural implementation in the codebase. This agent should be invoked proactively when: Context: Main agent is implementing a new feature for a data listing page. user: "I need to add functionality…