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-forgegit 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-forge)<a href="https://agentmods.dev/skills/dong90/oh-my-taiyiforge/taiyi-forge"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-forge/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-forge"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-forge.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.00038 | $0.01091 |
| Opus 5 | $0.00019 | $0.00545 |
| Sonnet 5 | $0.00008 | $0.00218 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
taiyi-forge 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taiyi-forge（引擎 Skill）
原则
- 用户只说
/taiyi:*（Codex：$taiyi-*）；你代跑scripts/taiyi-forge.sh，禁止让用户手打 shell。 - 读状态默认：
status [slug] --json --compact→ 解析engineTruth。以 engineTruth 为准，不以对话记忆为准。 - 写工件 →
/taiyi:write，编辑{phase}.json，再/taiyi:render刷新 md，然后加载当前阶段taiyi-change…taiyi-integrationSkill。
主流程（仅这五条）
| 斜杠 | 引擎 |
|---|---|
/taiyi:new |
new |
/taiyi:status |
status --json --compact |
/taiyi:write |
write |
/taiyi:render |
render [slug] [phase] — json→md（Zod+hbs） |
/taiyi:continue |
continue |
/taiyi:apply |
apply（dev/test） |
/taiyi:archive |
archive |
其余斜杠（doctor、audit、ralph、token 等）→ docs/taiyi/canonical-commands.md · docs/taiyi/commands.yaml
执行协议（破坏性操作）
| 斜杠 | HALT-AND-VERIFY 协议 |
|---|---|
/taiyi:continue |
必须在运行前展示 engineTruth 当前阶段 + 即将执行的命令。不跳过审核。 |
/taiyi:commit |
1. 跑 commit-trailers → 2. 展示建议 commit message + 变更摘要 → 3. 等待用户明确确认 → 4. 跑 commit |
/taiyi:ship |
1. 展示 PR diff 摘要 + 涉及的阶段 → 2. 等待用户确认 |
/taiyi:archive |
1. 展示归档 slug 名称 + 最终变化 → 2. 确认后执行 |
所有修改 git 历史 / 推送 / 部署的操作：展示完整计划并等待 "go ahead" 或 "yes" 才执行。
Token 纪律
| # | 动作 |
|---|---|
| 1 | 清 slug — archive / cancel --remove-dir；只保留 1 个 active |
| 2 | archive 闭环 — integration 后立刻 archive |
| 3 | compress — /taiyi:token compress <slug> → 读 CONTEXT-COMPACT.md |
| 4 | E2E 别在对话跑 — CI/后台；聊天只写 TEST.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 · 73 lines · 38 tokens per session scan A 55a77a757453
taiyi-forge is a skill published in the GitHub repository Dong90/oh-my-taiyiforge (888 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 1,091 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…