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 skills/cloud99277/kitclaw/agent-orchestratornpx skills add cloud99277/KitClaw --skill agent-orchestratorgit clone --depth 1 https://github.com/cloud99277/KitClawWrote 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/cloud99277/kitclaw/agent-orchestrator)<a href="https://agentmods.dev/skills/cloud99277/kitclaw/agent-orchestrator"><img src="https://agentmods.dev/badge/skills/cloud99277/kitclaw/agent-orchestrator.svg" alt="Measured on agentmods" 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 | $0.00132 | $0.00512 |
| Opus 5 | $0.00066 | $0.00256 |
| Sonnet 5 | $0.00026 | $0.00102 |
| Haiku 4.5 | $0.00013 | $0.00051 |
Grade A, and why
agent-orchestrator 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 3d 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
Agent Orchestrator — 线性链式 Skill 编排
定位
基于 Phase 1 IO 契约的线性链式编排 MVP。读取 YAML 编排链定义，验证相邻 skill 的 IO 类型匹配，输出分步执行计划。
不是执行器：orchestrator 验证链的合法性并生成执行指引，不直接调用 agent 执行 skill。
核心能力
- validate — 验证编排链的 IO 类型匹配（精确匹配 + 兼容匹配）
- plan — 输出带变量替换的分步执行指引
- list — 列出所有已注册的预定义编排链
使用方式
# 验证链
python3 scripts/run-chain.py validate chains/translate-tweet-publish.yaml
# 生成执行计划（带变量）
python3 scripts/run-chain.py plan chains/translate-tweet-publish.yaml --var URL=https://x.com/...
# 列出所有链
python3 scripts/run-chain.py list
编排链 YAML 格式
见 references/chain-schema.md。
依赖
- Phase 1 IO 契约（
type-registry.json、skill frontmatterio:声明） - 零外部依赖（纯 Python stdlib）
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- chains/auto-post-to-x.yaml 365 B
- chains/finalize-package.yaml 892 B
- chains/lint-and-search.yaml 455 B
- chains/prepare-draft.yaml 629 B
- chains/translate-tweet-publish.yaml 490 B
- chains/url-translate-publish.yaml 489 B
- chains/video-parse-from-url.yaml 913 B
- chains/video-parse-local.yaml 619 B
- references/chain-schema.md 3.1 KB
- scripts/run-chain.py 22 KB runs code
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.
- 3d ago First seen · 51 lines · 132 tokens per session scan A 8feb9066beb3
agent-orchestrator is a skill published in the GitHub repository cloud99277/KitClaw (5 stars, last pushed 4mo ago), licensed MIT. It adds 132 tokens to every session and 512 once invoked, about $0.0007 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…