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-ultraworkgit 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-ultrawork)<a href="https://agentmods.dev/skills/dong90/oh-my-taiyiforge/taiyi-ultrawork"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-ultrawork/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-ultrawork"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-ultrawork.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.00039 | $0.00460 |
| Opus 5 | $0.00019 | $0.00230 |
| Sonnet 5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
taiyi-ultrawork 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.
What it actually says
taiyi-ultrawork
加载时机：/taiyi:ultrawork · 关键词 ulw · scripts/taiyi-forge.sh ultrawork · ultrawork step 输出。
强制契约（TAIYI_ULW_AUTO_TASK=1 或 step 标明 AUTO）
- 主会话 禁止 亲自实现全部 TASK 切片。
- 对
step输出的每个 worker 并行 调用 CursorTask工具（或 Claude subagent）。 - 每个 worker prompt 须含：
/taiyi:agent <role>· 切片任务 ·/taiyi:sp test-driven-development· 完成标准 ralph 绿。 - 文件所有权清单：每个 worker prompt 必须附带其 write_files 清单 + 锁定表，标明：
- 该 worker 拥有 的文件（独占写权限）
- 该 worker 不可触碰 的文件（属其他 worker）
- 违反此规定 → 合并冲突，worker 需 rebase 重试
- 全部 worker 返回后：主会话合并冲突（如有）→
scripts/taiyi-forge.sh ralph→/taiyi:continue。 - 停止：
/taiyi:stop-mode。
辅助 Skill
/taiyi:sp dispatching-parallel-agents/taiyi:sp subagent-driven-development
引擎
scripts/taiyi-forge.sh step [slug] --mode ultrawork
环境变量：
| 变量 | 说明 |
|---|---|
TAIYI_ULW_TASK=0 |
不打印 Task 示例 |
TAIYI_ULW_AUTO_TASK=1 |
step 输出强制 AUTO 派发契约 |
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 · 39 lines · 39 tokens per session scan A 8e46a79d2a9c
taiyi-ultrawork is a skill published in the GitHub repository Dong90/oh-my-taiyiforge (888 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 460 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…