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-changegit 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-change)<a href="https://agentmods.dev/skills/dong90/oh-my-taiyiforge/taiyi-change"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-change/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-change"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 17 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 115 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00025 | $0.02151 |
| Opus 5 | $0.00013 | $0.01076 |
| Sonnet 5 | $0.00005 | $0.00430 |
| Haiku 4.5 | $0.00003 | $0.00215 |
Grade A, and why
taiyi-change scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- 每条可验证：curl / npm test / UI 操作步骤 How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taiyi-change — 变更提案
进入本阶段前请优先读
.taiyi/changes/<slug>/PHASE-CONTEXT.md（~500 tokens），不要全量加载上游工件。
框架集成
本阶段使用以下框架：
| 框架 | 用途 | 何时加载 |
|---|---|---|
| Harness | 阶段门禁与推进（status → continue；legacy：npx taiyi complete） |
全程 |
| OMO | 作为 workflow 入口，承接 /taiyi:new 命令 |
进入时 |
| Superpowers | brainstorming — 可选，当需求不清晰时加载协助梳理 |
可选 |
| OpenSpec | 将 CHANGE.md 同步到 openspec/changes/<slug>/ |
可选（taiyi sync-openspec） |
Spec-Kit 和 GStack 在本阶段不涉及。
前置门禁（Pre-flight）
0.1 架构级变更检测
命中任一 → 反问用户确认：
- 改模块结构（新增/拆分/合并目录）
- 动 ADR（架构决策记录）
- 改公共契约（API 签名、CLI 参数、DB Schema）
- 跨服务编排（涉及 2+ 独立服务）
0.2 Profile 判定
| Profile | CHANGE.md 要求 |
|---|---|
full |
完整：Motivation + In/Out Scope + Risks + Success Criteria |
api/ui |
同上，Out of scope ≥ 1 条 |
lite |
可省略 Risks 段，其余照常 |
micro/spike |
仅 Motivation + Success Criteria，Out of scope 可选 |
nano |
可跳过本阶段（引擎自动通过） |
0.3 前置检查清单
- slug 命名合理（小写+连字符，如
fix-login-timeout） - 用户已确认变更目标（不是 AI 自己推断的需求）
- 不与其他活跃 change 的 Scope 重叠（
taiyi list确认）
步骤
工件契约
| 层 | 路径 | 职责 |
|---|---|---|
| 语义真源 | change.json |
Zod（src/schemas/change.ts）— Agent 优先编辑 |
| 生成视图 | CHANGE.md |
hbs（src/templates/change.hbs）— 人读 / PR |
| 流程 | 本 Skill | 门禁、写作纪律、下游衔接 |
工作流：编辑 json → scripts/taiyi-forge.sh render <slug> change → status --json --compact → 用户确认 → continue --approver "名"。
详见 docs/taiyi/artifact-contract.md。
json 字段（Zod 摘要）
| 字段 | 要求 |
|---|---|
title |
描述性标题 |
motivation |
谁痛、现状代价、改善指标（具体，不笼统） |
scope.includes |
In scope 条目 |
scope.excludes |
≥1 条 Out of scope；关联 change 写 slug |
success_criteria |
≥1 条；id + description；每条可映射到测试 |
risks |
full/api 推荐：risk / probability / impact / mitigation |
impact_map |
可选；模块影响面声明 |
evidence |
success_criteria[].is_checked=true 时必填真跑命令 |
1. 编辑 change.json
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.
- 12d ago First seen · 164 lines · 25 tokens per session scan A fd02a9fc300f
taiyi-change is a skill published in the GitHub repository Dong90/oh-my-taiyiforge (888 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 2,151 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…