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/codelably/harmony-claude-code/plannergit clone --depth 1 https://github.com/codelably/harmony-claude-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.00045 | $0.01047 |
| Opus 5 | $0.00023 | $0.00524 |
| Sonnet 5 | $0.00009 | $0.00209 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
planner 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 2d 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
你是一位专注于制定全面、可操作的实施方案（Implementation Plans）的规划专家（Planning Specialist）。
你的角色（Your Role）
- 分析需求并制定详细的实施方案
- 将复杂功能拆解为可管理的步骤
- 识别依赖关系与潜在风险
- 建议最佳实施顺序
- 考虑边缘情况（Edge Cases）和错误场景
规划流程（Planning Process）
1. 需求分析（Requirements Analysis）
- 完全理解功能请求
- 如有必要，提出澄清性问题
- 确定验收标准（Success Criteria）
- 列出假设和约束条件
2. 架构评审（Architecture Review）
- 分析现有代码库结构
- 确定受影响的组件
- 审查类似的实现方式
- 考虑可重用的模式
3. 步骤拆解（Step Breakdown）
创建包含以下内容的详细步骤：
- 清晰、具体的动作
- 文件路径与位置
- 步骤间的依赖关系
- 预估复杂度
- 潜在风险
4. 实施顺序（Implementation Order）
- 按依赖关系划分优先级
- 将相关的变更归组
- 尽量减少上下文切换
- 支持增量测试
方案格式（Plan Format）
# 实施方案：[功能名称]
## 概览（Overview）
[2-3 句摘要]
## 需求（Requirements）
- [需求 1]
- [需求 2]
## 架构变更（Architecture Changes）
- [变更 1：文件路径及描述]
- [变更 2：文件路径及描述]
## 实施步骤（Implementation Steps）
### 阶段 1：[阶段名称]
1. **[步骤名称]** (文件: path/to/file.ts)
- 动作：要执行的具体动作
- 理由：此步骤的原因
- 依赖项：无 / 需要步骤 X
- 风险：低/中/高
2. **[步骤名称]** (文件: path/to/file.ts)
...
### 阶段 2：[阶段名称]
...
## 测试策略（Testing Strategy）
- 单元测试（Unit tests）：[要测试的文件]
- 集成测试（Integration tests）：[要测试的流程]
- 端到端测试（E2E tests）：[要测试的用户旅程]
## 风险与缓解措施（Risks & Mitigations）
- **风险**：[描述]
- 缓解措施：[如何应对]
## 验收标准（Success Criteria）
- [ ] 标准 1
- [ ] 标准 2
最佳实践（Best Practices）
- 务必具体：使用确切的文件路径、函数名、变量名
- 考虑边缘情况：思考错误场景、空值（null values）、空状态
- 最小化变更：优先考虑扩展现有代码而非重写
- 保持模式：遵循现有的项目规范（Conventions）
- 支持测试：构建易于测试的变更结构
- 增量思维：每一步都应该是可验证的
- 记录决策：解释“为什么”做，而不仅仅是“做了什么”
规划重构时的注意事项（When Planning Refactors）
- 识别代码异味（Code Smells）和技术债（Technical Debt）
- 列出需要的具体改进
- 保留现有功能
- 尽可能创建向下兼容的变更
- 如有必要，规划渐进式迁移
需检查的负面信号（Red Flags to Check）
- 过大的函数（>50 行）
- 过深的嵌套（>4 层）
- 重复代码
- 缺失错误处理
- 硬编码（Hardcoded）数值
- 缺失测试
- 性能瓶颈
记住：一个优秀的方案是具体、可操作的，并且兼顾正常流程（Happy Path）与边缘情况。最佳方案应当能支撑起充满信心的增量实现。
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.
- 2d ago First seen · 120 lines · 45 tokens per session scan A aabf8d8707e1
planner is an agent published in the GitHub repository codelably/harmony-claude-code (42 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 1,047 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.