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 Dong90/oh-my-taiyiforge --skill taiyi-orchestratorgit clone --depth 1 https://github.com/Dong90/oh-my-taiyiforgeWrote 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/dong90/oh-my-taiyiforge/taiyi-orchestrator)<a href="https://agentmods.dev/skills/dong90/oh-my-taiyiforge/taiyi-orchestrator"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-orchestrator/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/dong90/oh-my-taiyiforge/taiyi-orchestrator"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.01286 |
| Opus 5 | $0.00026 | $0.00643 |
| Sonnet 5 | $0.00010 | $0.00257 |
| Haiku 4.5 | $0.00005 | $0.00129 |
Grade A, and why
taiyi-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 13d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taiyi-orchestrator
This is a ROUTER ONLY. Your job ends after Step 8 — do NOT execute scripts/taiyi-forge.sh or any shell command directly. DO NOT implement code, run tests, or write artifacts. Once you have loaded the phase skill and output the route declaration, your work is done.
Goal
解析用户意图，自动：1) 读项目状态 2) 工件前置检查 3) 意图路由 4) Token预算估选挡位 5) 路由声明 6) 进入对应Skill
Workflow
第一步 · 读取项目状态（引擎真源）
读 .taiyi/changes/<slug>/state.json 的 currentPhase / completedPhases / workflowStatus。
或用 jq 提取：jq -r '{currentPhase, completedPhases, workflowStatus}' .taiyi/changes/<slug>/state.json
这是阶段状态的唯一真源，不是对话记忆。
第二步 · Artifact Preflight Gate
路由前检查上游工件是否齐全，缺失→回退补齐。
第三步 · Token预算 + 挡位
估算token消耗，让用户选挡位（完整/极简/单点/不走flow）。成本因子：前端+20%、schema变更+10%、task<3→-30%、task>10→+50%
第四步 · 老项目入场检测
探测 AGENTS.md / CLAUDE.md / .cursor/rules/ 等已有AI文档，反问用户处理方式。
第五步 · 意图匹配 & 路由（含跨阶段防护）
- 按关键词匹配阶段（继续→dev、审查→review、测试→test、设计→design等）
- 跨阶段防护：如果用户请求涉及代码改动/测试/审查，但 engineTruth 当前阶段不是 dev/test/review，则 HALT 并提问："当前处于 [phase] 阶段。你要先完成当前阶段，还是手动切换到 [匹配] 阶段？"
- 如果用户请求与当前阶段无关（如问项目架构），允许——不阻挠纯信息问题。
第六步 · 路由声明（必须）
进入前输出：路由/Change-ID/已加载/未加载/Token预算/第一动作
第七步 · 加载工件策略
每阶段标注必读vs按需，控制token消耗。优先读 .taiyi/changes/<slug>/PHASE-CONTEXT.md（~500 tokens），不要全量加载上游工件。
第八步 · 执行对应Skill（附关闭协议）
- 加载当前阶段的 Skill（
taiyi-change…taiyi-integration） - 进入 phase skill 后 orchestrator 职责结束。从此刻起你的任务是 phase skill 中的阶段步骤，不要再返回 orchestrator 的路由/预算/挡位决策逻辑。
- 如果刚刚执行了
continue并成功：立即重新读取 engineTruth。如果currentPhase已变化，切换到新阶段的 Skill 并通知用户。不要继续用旧阶段逻辑处理。
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.
- 13d ago First seen · 84 lines · 51 tokens per session scan A 671a967c8572
taiyi-orchestrator is a skill published in the GitHub repository Dong90/oh-my-taiyiforge (888 stars, last pushed 5d ago), licensed MIT. It adds 51 tokens to every session and 1,286 once invoked, about $0.0003 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 skills, from other repositories
review
Use when the user wants code assessed rather than changed — "review PR 88", "is this branch ready to merge?", "look over my changes", "any problems with this diff?", "give me a code review", "what do you think of this PR?", "sanity-check this branch", "ship it?". Applies to a pull request or the current branch when…
fix
PRFlow's code-review reception skill (formerly receiving-code-review), used by the review-and-fix loop and available directly. Use when addressing review feedback already posted on a pull request — verifying findings before applying them — as distinct from /prflow:review-and-fix, which runs the review itself and then…
review-and-fix
Use when the user wants problems in a pull request or the current branch both found AND corrected — "review my changes and fix what's wrong", "clean up whatever the review turns up", "address the review feedback on this branch", "tidy this PR up before merge", "find and fix the issues here". Requires explicit fix…
docs-bootstrap-internal
Use when a codebase has no structured developer documentation yet and needs it built from scratch — "we have no docs at all", "set up internal docs for this repo", "the docs directory is a mess, start over", "create developer documentation for this codebase" — including an empty or disorganized docs directory or a…
docs-release-notes
Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…
docs-sync-internal
Use when code changes on the current branch need matching internal or developer documentation — "update our internal docs", "the architecture docs are stale after this change", "document what I just changed", "do the dev docs still match the code?" — or as a pre-push check that developer docs track the code. Narrower…