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-plangit 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-plan)<a href="https://agentmods.dev/skills/dong90/oh-my-taiyiforge/taiyi-plan"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-plan/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-plan"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-plan.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.00052 | $0.04777 |
| Opus 5 | $0.00026 | $0.02388 |
| Sonnet 5 | $0.00010 | $0.00955 |
| Haiku 4.5 | $0.00005 | $0.00478 |
Grade A, and why
taiyi-plan 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taiyi-plan
目的
作为 TaiyiForge 的规划阶段，在 /taiyi:new 之前运行。把一份大的需求文档（README、PRD、技术方案）拆成一组互不阻塞的 change，每个 change 带推荐 profile、依赖关系和优先级，然后批量创建。
何时使用
/taiyi:plan 跑在九阶段之前，是整个流程的第一个入口：
/taiyi:plan（规划阶段）
│
▼ 产出 PLAN.md + 批量 /taiyi:new
│
┌────┴────┬────┬────┐
▼ ▼ ▼ ▼
change change change change（各自走九阶段）
| 信号 | 建议 |
|---|---|
| 新项目拿到 README / PRD，不知道从哪开始 | 必跑 |
| 大功能涉及多个模块，想做并行开发 | 必跑 |
| 需求文档包含 5 个以上独立功能点 | 必跑 |
| 只有一个 typo 或单文件改动 | 跳过 |
何时不用
- 单文件改动，直接
/taiyi:new走 micro - 已经有了完整的 slug 清单
- 纯技术改动（升级依赖、修 lint）直接 micro/nano
输入
/taiyi:plan 可以接文件路径，支持任何能读出文字的内容：
| 输入 | 用法 | 提取方式 | 工具 |
|---|---|---|---|
| 本地 Markdown | /taiyi:plan docs/PRD.md |
Read 直接读取 |
内置 |
| 纯文本 | /taiyi:plan requirements.txt |
Read 直接读取 |
内置 |
/taiyi:plan docs/spec.pdf |
look_at 或 pdftotext 提取文本 |
look_at / pdftotext |
|
| Word 文档 | /taiyi:plan docs/设计文档.docx |
python-docx 或 pandoc 转文本 |
python-docx / pandoc |
| 网页 / 在线文档 | /taiyi:plan https://wiki.example.com/prd |
webfetch 抓取后解析 |
webfetch |
| 不指定文件 | /taiyi:plan |
自动找 README.md，找不到则询问 | glob **/README.md |
执行方式：
- 读取指定文件 → 提取全部文字内容
- 如果是非文本格式（PDF/docx），先用对应工具提取文本（PDF 优先
look_at，docx 回退到python-docx） - 将提取的文字作为需求输入，进入正常的拆解流程
自动模式（--auto）
/taiyi:plan README.md --auto 与普通模式的核心区别：
| 维度 | 普通模式 | --auto 模式 |
|---|---|---|
| 用户确认 | 必须等用户确认后再创建 | 跳过用户确认，拆完即创建 |
| 拆解计划 | 写到 .taiyi/PLAN.md + 聊天审阅 |
直接写到 .taiyi/PLAN.md，不展开聊 |
| Profile 选择 | 按决策树问用户 | 按决策树自动判断（拿不准时默认 full） |
| 创建方式 | 用户选"自动创建"才批量 /taiyi:new |
立即批量 /taiyi:new |
| 交互节奏 | 慢：展示 → 确认 → 创建 | 快：一行命令跑完 |
执行差异：
- 依然需要走完"读取需求 → 识别模块 → 冲突检测 → 拆解计划"全部步骤
- 拆解计划写完后，不等用户确认，直接进入批量创建（Step 6）
- 创建完成后输出汇总，用户直接进入
/taiyi:status看进度 --auto模式下如果遇到模棱两可的选择（如不确定用 full 还是 api），往大选（full > api > lite），宁浪费一点流程也不能漏掉关键步骤
--auto不改变拆解逻辑，只改变确认节奏。用户信任 AI 的拆解判断时可省一次来回。
输出
一份结构化拆解计划，写到 .taiyi/PLAN.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.
- 13d ago First seen · 394 lines · 52 tokens per session scan A f4390ff96104
taiyi-plan is a skill published in the GitHub repository Dong90/oh-my-taiyiforge (888 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 4,777 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…