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-diagram-flowgit 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-diagram-flow)<a href="https://agentmods.dev/skills/dong90/oh-my-taiyiforge/taiyi-diagram-flow"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-diagram-flow/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-diagram-flow"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-diagram-flow.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.00044 | $0.01213 |
| Opus 5 | $0.00022 | $0.00607 |
| Sonnet 5 | $0.00009 | $0.00243 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
taiyi-diagram-flow 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taiyi-diagram-flow
目的
把需求里的用户路径、阶段门禁、错误分支、状态迁移画成可执行的流程图——供 TASK.md 切片、taiyi-dev 实现与 taiyi-test 用例一一对应。
何时使用
| 时机 | 说明 |
|---|---|
taiyi-design 有复杂分支/异步 |
主流程 + 异常流 |
taiyi-task 拆切片前 |
每切片应对齐流程中的一段 |
| 九阶段 / harness / 门禁说明 | 工作流全景 flowchart |
taiyi-test 写 E2E 场景 |
Given/When/Then → 路径覆盖 |
可跳过：线性 CRUD、无分支、AC 已表格化且无歧义。
输入
REQUIREMENT.md（User Stories、AC）DESIGN.md（状态、API、错误码）TASK.md（若补画 dev 级细节）- （可选）
docs/taiyi/workflow-manifest.yaml（官方九阶段顺序）
输出
| 产物 | 路径 |
|---|---|
| 主流程图 | .taiyi/changes/<slug>/diagrams/flows.md |
| 子流程 | .taiyi/changes/<slug>/diagrams/flow-<name>.md |
| 嵌入 | REQUIREMENT.md / TASK.md / TEST.md 内 mermaid 块 |
mark-aux：scripts/taiyi-forge.sh mark-aux <slug> taiyi-diagram-flow（当 diagrams/flows.md 或子文件已写入实质内容）。
图类型选型
| 场景 | Mermaid 类型 |
|---|---|
| 用户/业务步骤 | flowchart TD 或 flowchart LR |
| API / 模块调用时序 | sequenceDiagram |
| 订单/任务/变更状态 | stateDiagram-v2 |
| 并行网关 | flowchart + fork 节点说明 |
| 九阶段推进 | flowchart LR + subgraph 阶段 |
执行步骤
- 从 AC 提取路径：每条 AC 至少对应图中一条从入口到终态的路径
- 标门禁节点：人工门（change/design/review）、quality gate、delivery gate 用 菱形
{ }或[门禁: …] - 标失败边：每个决策点须有 否 分支（回退、重试、abort）——禁止只画 happy path
- 写 flows.md：
# Flow Diagrams: <slug>
## Main user flow
\`\`\`mermaid
flowchart TD
A[用户提交] --> B{校验}
B -->|通过| C[写入]
B -->|失败| D[4xx + 消息]
C --> E[完成]
\`\`\`
## Taiyi 九阶段（本变更）
\`\`\`mermaid
flowchart LR
change --> requirement --> design --> task --> dev --> test --> review --> integration
\`\`\`
## Traceability
| 节点 | AC / TASK |
|------|-----------|
| B | AC-2 |
| C | TASK-1 |
- （可选）导出 PNG：
node scripts/render-mermaid.mjs diagrams/flows.md - 回链 TASK.md：每个切片标题旁注
(flow: Main user flow → C) - mark-aux
命名与风格
- 节点 ID：
camelCase或snake_case，全文件唯一 - 用户可见文案用中文；内部模块用代码名（
workflow-engine） - 单图节点 ≤15；超出拆
flow-<topic>.md并在 flows.md 链过去 - 颜色（可选）：
classDef gate fill:#fef3c7标注门禁
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 · 115 lines · 44 tokens per session scan A 004efd9ae5c7
taiyi-diagram-flow is a skill published in the GitHub repository Dong90/oh-my-taiyiforge (888 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 1,213 once invoked, about $0.0002 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…