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 commands/luohaothu/everything-codex/orchestrategit 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.00000 | $0.00897 |
| Opus 5 | $0.00000 | $0.00449 |
| Sonnet 5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
orchestrate 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
编排命令
用于复杂任务的顺序代理工作流。
使用
/orchestrate [workflow-type] [task-description]
工作流类型
feature
完整功能实现工作流：
planner -> tdd-guide -> code-reviewer -> security-reviewer
bugfix
错误调查与修复工作流：
explorer -> tdd-guide -> code-reviewer
refactor
安全重构工作流：
architect -> code-reviewer -> tdd-guide
security
安全审查工作流：
security-reviewer -> code-reviewer -> architect
执行模式
针对工作流中的每个代理：
- 使用来自上一个代理的上下文调用代理
- 将输出收集为结构化的交接文档
- 将文档传递给链中的下一个代理
- 将结果汇总到最终报告中
交接文档格式
在代理之间，创建交接文档：
## 交接：[前一位代理人] -> [下一位代理人]
### 背景
[已完成工作的总结]
### 发现
[关键发现或决定]
### 已修改的文件
[已触及的文件列表]
### 待解决的问题
[留给下一位代理人的未决事项]
### 建议
[建议的后续步骤]
示例：功能工作流
/orchestrate feature "Add user authentication"
执行：
-
规划代理
- 分析需求
- 创建实施计划
- 识别依赖项
- 输出：
HANDOFF: planner -> tdd-guide
-
TDD 指导代理
- 读取规划交接文档
- 先编写测试
- 实施代码以通过测试
- 输出：
HANDOFF: tdd-guide -> code-reviewer
-
代码审查代理
- 审查实现
- 检查问题
- 提出改进建议
- 输出：
HANDOFF: code-reviewer -> security-reviewer
-
安全审查代理
- 安全审计
- 漏洞检查
- 最终批准
- 输出：最终报告
最终报告格式
ORCHESTRATION REPORT
====================
Workflow: feature
Task: Add user authentication
Agents: planner -> tdd-guide -> code-reviewer -> security-reviewer
SUMMARY
-------
[One paragraph summary]
AGENT OUTPUTS
-------------
Planner: [summary]
TDD Guide: [summary]
Code Reviewer: [summary]
Security Reviewer: [summary]
FILES CHANGED
-------------
[List all files modified]
TEST RESULTS
------------
[Test pass/fail summary]
SECURITY STATUS
---------------
[Security findings]
RECOMMENDATION
--------------
[SHIP / NEEDS WORK / BLOCKED]
并行执行
对于独立的检查，并行运行代理：
### 并行阶段
同时运行：
- code-reviewer（质量）
- security-reviewer（安全）
- architect（设计）
### 合并结果
将输出合并为单一报告
参数
$ARGUMENTS:
feature <description>- 完整功能工作流bugfix <description>- 错误修复工作流refactor <description>- 重构工作流security <description>- 安全审查工作流custom <agents> <description>- 自定义代理序列
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 · 184 lines · 0 tokens per session scan A da428e67e29c
orchestrate is a command published in the GitHub repository Luohaothu/everything-codex (24 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 897 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.