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-requirementgit 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-requirement)<a href="https://agentmods.dev/skills/dong90/oh-my-taiyiforge/taiyi-requirement"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-requirement/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-requirement"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-requirement.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 202 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.00027 | $0.02692 |
| Opus 5 | $0.00014 | $0.01346 |
| Sonnet 5 | $0.00005 | $0.00538 |
| Haiku 4.5 | $0.00003 | $0.00269 |
Grade A, and why
taiyi-requirement 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| AC-1.1 | SC-1（API 返回 200） | curl -s -w '%{http_code}' POST /api/translate | How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taiyi-requirement — 需求分析
进入本阶段前请优先读
.taiyi/changes/<slug>/PHASE-CONTEXT.md（~500 tokens），不要全量加载上游工件。
框架集成
本阶段使用以下框架：
| 框架 | 用途 | 何时加载 |
|---|---|---|
| Harness | 阶段门禁与推进（status → continue；legacy：npx taiyi complete） |
全程 |
| OpenSpec | 将 REQUIREMENT.md 同步到 openspec 格式 | 可选 |
Superpowers / GStack / Spec-Kit / OMO 在本阶段不涉及。
前置门禁（Pre-flight）
0.1 上游检查
- change 阶段已过关（
engineTruth.completedPhases含change或currentPhase已推进） - 无跨 change 的 AC 冲突（
taiyi list检查其他活跃 change 的 scope）
0.2 Profile 判定
| Profile | REQUIREMENT.md 要求 |
|---|---|
full |
完整：User Stories + AC(Given/When/Then) + 域语言 + Traceability |
api/ui |
User Stories + AC，域语言可选 |
lite |
仅 AC 列表，可省 User Stories |
micro/spike |
可跳过本阶段 |
nano |
跳过 |
0.3 触发者检查
每个 FR 必须声明触发点：
- 每个 FR 必须填写
trigger（谁调用、什么时机） trigger指向的caller_module不在本 change scope 中 → 填blocked_by标注依赖blocked_by非空 → 本阶段不能过关，等依赖 change 完成后再继续
"functional_requirements": [{
"module": "orchestrator",
"items": [{
"id": "FR-T01",
"description": "track(slug,role,amount) 更新 pipeline.json tokenBudget.used",
"trigger": "executor.dispatch() 每次调用后",
"caller_module": "packages/orchestrator/src/executor.ts",
"blocked_by": "M4-executor"
}]
}]
blocked_by 非空时引擎会在 status 中报 blocker，阻止进入 design 阶段。
0.4 前置检查清单
- change 阶段已过关
- 理解 CHANGE Scope 和 Out of Scope 边界
- 每个 FR 有 trigger（谁调用、什么时机）；caller 不在 scope 时填 blocked_by
步骤
工件契约
| 层 | 路径 | 职责 |
|---|---|---|
| 语义真源 | requirement.json |
Zod（src/schemas/requirement.ts） |
| 生成视图 | REQUIREMENT.md |
hbs（src/templates/requirement.hbs） |
| 流程 | 本 Skill | US / AC / 域语言 / Traceability 纪律 |
工作流：编辑 json → scripts/taiyi-forge.sh render <slug> requirement → status → continue。
详见 docs/taiyi/artifact-contract.md。
json 字段（Zod 摘要）
| 字段 | 要求 |
|---|---|
title |
一句话概括核心需求 |
features |
核心功能点列表 |
scope_out |
明确排除项（对齐 CHANGE scope.excludes） |
acceptance_criteria |
≥1 条；id + description；Given/When/Then 写在 description |
functional_requirements |
可选；按模块组织 |
non_functional |
可选；performance / security / availability |
error_rescue_map |
可选；错误 → 用户可见 → 恢复 |
shadow_paths / non_happy_path_cases |
可选；边界与非快乐路径 |
dependencies |
可选；外部依赖与风险 |
evidence |
AC 标 is_checked=true 时必填 |
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 · 248 lines · 27 tokens per session scan A ec9676a29152
taiyi-requirement is a skill published in the GitHub repository Dong90/oh-my-taiyiforge (888 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 2,692 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…