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 skills add Xwen0857/agent-orchestrator --skill planner-opsgit clone --depth 1 https://github.com/Xwen0857/agent-orchestratorWrote 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/skills/xwen0857/agent-orchestrator/planner-ops)<a href="https://agentmods.dev/skills/xwen0857/agent-orchestrator/planner-ops"><img src="https://agentmods.dev/badge/skills/xwen0857/agent-orchestrator/planner-ops/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/xwen0857/agent-orchestrator/planner-ops"><img src="https://agentmods.dev/badge/skills/xwen0857/agent-orchestrator/planner-ops.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.03161 |
| Opus 5.5 | $0.00016 | $0.01264 |
| Sonnet 5.5 | $0.00008 | $0.00632 |
| Haiku 4.5 | $0.00004 | $0.00316 |
Grade A, and why
planner-ops 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 1mo 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Ops
V2 基线（强制优先）
- planner-ops 必须在
templates/coordination/tasks/task_folders/<task_id>/meta.json上进行状态推进，禁止通过*_tasks.md推断真实状态。 CREATED -> PLANNED -> ASSIGNED为 planner 主负责链路，转移时必须校验meta.version并追加事件日志。- 所有分配动作必须生成
operation_id（幂等键）；重试时复用同一operation_id，不得重复生效。 - 每次任务分配都必须落地
plan.md追溯字段（primary_id/checklist_item_id/subchecklist_id）并在meta.artifacts中声明。 - 兼容镜像仍可生成到
templates/coordination/tasks/<worker_id>_tasks.md，但运行态 worker 任务与 subchecklist 记录已迁至仓外状态目录。
核心职责
- 接收并维护用户原始需求入口文件
primary.md。 - 在接收到启动指令后，将
primary拆解为checklist。 - 将
checklist拆解为可执行subchecklist，并建立追溯关系。 - 将
subchecklist进一步拆解并分配为 worker 可直接执行的任务文件。 - 维护任务状态机、worker 生命周期、替换映射与替换日志。
- 读取 tester 验收结果，驱动重试、替换或任务收敛。
输入文件相对路径
- primary 需求入口运行路径：
$AGENT_ORCHESTRATOR_STATE_DIR/planner/primary.md（默认~/.openclaw-state/agent-orchestrator/planner/primary.md）。 - checklist 运行记录路径：
$AGENT_ORCHESTRATOR_STATE_DIR/planner/checklist.md（若未设置，则默认~/.openclaw-state/agent-orchestrator/planner/checklist.md）。 - checklist 示例模板路径：
templates/coordination/planner/checklist.example.md。 - subchecklist 运行目录路径：
$AGENT_ORCHESTRATOR_STATE_DIR/tasks/subchecklists（默认~/.openclaw-state/agent-orchestrator/tasks/subchecklists）。 - worker 任务运行目录路径：
$AGENT_ORCHESTRATOR_STATE_DIR/tasks/worker_tasks（默认~/.openclaw-state/agent-orchestrator/tasks/worker_tasks）。 - 兼容 worker 任务路径（旧）：
templates/coordination/tasks/<worker_id>_tasks.md。
输出文件相对路径
- checklist 运行记录路径：
$AGENT_ORCHESTRATOR_STATE_DIR/planner/checklist.md（默认~/.openclaw-state/agent-orchestrator/planner/checklist.md）。 - subchecklist 运行文件路径：
$AGENT_ORCHESTRATOR_STATE_DIR/tasks/subchecklists/<subchecklist_id>.md。 - worker 任务运行文件路径：
$AGENT_ORCHESTRATOR_STATE_DIR/tasks/worker_tasks/<worker_id>_tasks.md。 - worker 状态文件路径：
templates/coordination/workers/<worker_id>_worker.md。 - worker 生命周期文件路径：
templates/coordination/worker_lifecycle/<worker_id>_lifecycle.md。 - 替换日志路径：
templates/coordination/replacement_log.md。 - 替换映射路径：
templates/coordination/worker_replacement_mapping.md。
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.
- 1mo ago First seen · 154 lines · 40 tokens per session scan A d8d34ef1cc10
planner-ops is a skill published in the GitHub repository Xwen0857/agent-orchestrator (2 stars, last pushed 7mo ago), licensed MIT. It adds 40 tokens to every session and 3,161 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
orca-replay
Answers questions about a past agent run from its recording rather than from memory, and replays or forks that run. Use when asked why an earlier run did something, or to reproduce a failure.
adversarial-review
A multi-stage code review process in which one reviewer looks for failures, another independently checks the findings and the changed code, and a final reviewer decides which findings stand. It requires evidence such as code locations or test results and states that the reviewers may still share the same model's blind spots.
decision-matrix
Compare options with weighted scoring, pros and cons, pre-mortems, opportunity costs, and ICE prioritization. Use when a user wants to reason through a choice, expose assumptions, or rank alternatives.
meeting-note-summarizer
Turn meeting notes or transcripts into factual summaries, decisions, questions, and action items. Use when a user wants a concise recap or needs explicit owners and deadlines extracted without filling in missing details.
skillhub-cli
Connect an Agent to a SkillHub registry and use the official SkillHub CLI to search, install, list, or explicitly upgrade SkillHub skills. Use when a user asks to connect SkillHub, install a SkillHub skill, or manage skills previously installed from SkillHub.
ledger-tasks-yylo
Comprehensive guide for using YYLO Ledger task management without bypassing controller routing, lifecycle state, or mutation receipts. Covers task commands, dependency management, best practices, and workflow patterns. Use when you need to interact with the YYLO Ledger board.