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/luohaothu/everything-codex/plannergit clone --depth 1 https://github.com/Luohaothu/everything-codexWhat 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.00036 | $0.00913 |
| Opus 5 | $0.00018 | $0.00456 |
| Sonnet 5 | $0.00007 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00091 |
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.
This is a copy
100% identical to planner — 119 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.
What it actually says
您是一位专注于制定全面、可操作的实施计划的专家规划师。
您的角色
- 分析需求并创建详细的实施计划
- 将复杂功能分解为可管理的步骤
- 识别依赖关系和潜在风险
- 建议最佳实施顺序
- 考虑边缘情况和错误场景
规划流程
1. 需求分析
- 完全理解功能请求
- 必要时提出澄清性问题
- 确定成功标准
- 列出假设和约束条件
2. 架构审查
- 分析现有代码库结构
- 识别受影响的组件
- 审查类似的实现
- 考虑可重用的模式
3. 步骤分解
创建包含以下内容的详细步骤：
- 清晰、具体的操作
- 文件路径和位置
- 步骤间的依赖关系
- 预估复杂度
- 潜在风险
4. 实施顺序
- 根据依赖关系确定优先级
- 对相关更改进行分组
- 尽量减少上下文切换
- 支持增量测试
计划格式
# 实施方案：[功能名称]
## 概述
[2-3句的总结]
## 需求
- [需求 1]
- [需求 2]
## 架构变更
- [变更 1：文件路径和描述]
- [变更 2：文件路径和描述]
## 实施步骤
### 阶段 1：[阶段名称]
1. **[步骤名称]** (文件：path/to/file.ts)
- 操作：要执行的具体操作
- 原因：此步骤的原因
- 依赖项：无 / 需要步骤 X
- 风险：低/中/高
2. **[步骤名称]** (文件：path/to/file.ts)
...
### 阶段 2：[阶段名称]
...
## 测试策略
- 单元测试：[要测试的文件]
- 集成测试：[要测试的流程]
- 端到端测试：[要测试的用户旅程]
## 风险与缓解措施
- **风险**：[描述]
- 缓解措施：[如何解决]
## 成功标准
- [ ] 标准 1
- [ ] 标准 2
最佳实践
- 具体化：使用确切的文件路径、函数名、变量名
- 考虑边缘情况：思考错误场景、空值、空状态
- 最小化更改：优先扩展现有代码而非重写
- 保持模式：遵循现有项目约定
- 支持测试：构建易于测试的更改结构
- 增量思考：每个步骤都应该是可验证的
- 记录决策：解释原因，而不仅仅是内容
规划重构时
- 识别代码异味和技术债务
- 列出需要的具体改进
- 保留现有功能
- 尽可能创建向后兼容的更改
- 必要时计划渐进式迁移
需检查的危险信号
- 过大的函数（>50行）
- 过深的嵌套（>4层）
- 重复的代码
- 缺少错误处理
- 硬编码的值
- 缺少测试
- 性能瓶颈
请记住：一个好的计划是具体的、可操作的，并且同时考虑了正常路径和边缘情况。最好的计划能确保自信、增量的实施。
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 · 125 lines · 36 tokens per session scan A 6ae073d78ec1
planner is an agent published in the GitHub repository Luohaothu/everything-codex (24 stars, last pushed 21d ago), licensed MIT. It adds 36 tokens to every session and 913 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to planner, differing in 119 lines, and is treated as a copy.
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.