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-architectgit 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-architect)<a href="https://agentmods.dev/skills/dong90/oh-my-taiyiforge/taiyi-architect"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-architect/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-architect"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-architect.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.00044 | $0.01118 |
| Opus 5 | $0.00022 | $0.00559 |
| Sonnet 5 | $0.00009 | $0.00224 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
taiyi-architect 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taiyi-architect
目的
把长期难逆的技术决策从 DESIGN.md 抽成独立 ADR,供未来变更、onboarding 和 review 追溯——不替代 taiyi-design,而是补充「为什么当时这样选」。
何时使用
| 决策类型 | 示例 | 建议 |
|---|---|---|
| 数据与存储 | 新表、迁移策略、缓存层 | ADR |
| 安全与信任 | 鉴权模型、多租户隔离 | ADR |
| 集成边界 | 新微服务、第三方 SDK、事件总线 | ADR |
| 跨团队契约 | 公共 API、共享库破坏性变更 | ADR |
| 局部重构 | 重命名、抽函数 | 否,留在 DESIGN / TASK |
触发信号:
taiyi_assess推荐taiyi-architecttaiyi-designOptions 里多个方案 Cost 差 ≥ 2x 或 运维负担显著不同- dev 中发现原方案不可行,需正式废弃旧决策
输入
CHANGE.md、REQUIREMENT.md、DESIGN.md- (可选)
CONTEXT.md、taiyi-intel-scan风险区 - 工程评审结论
输出
- 路径:
.taiyi/changes/<slug>/adr/NNNN-<short-title>.md - 编号:
0001起递增,全仓库统一或每 slug 独立二选一(在首个 ADR 文首声明规则) DESIGN.md的 Decision 节须回链:ADR-0003+ 一句话摘要
ADR 结构(必填)
# ADR-NNNN: <标题>
## Status
proposed | accepted | deprecated | superseded by ADR-XXXX
## Context
<!-- 压力、约束、相关 AC / 风险 -->
## Decision
<!-- 我们决定 … -->
## Consequences
### Positive
- …
### Negative
- …
## Alternatives considered
| 方案 | 优点 | 缺点 | 为何未选 |
|------|------|------|----------|
| A | | | |
| B | | | |
## Links
- DESIGN.md §…
- REQUIREMENT.md AC-…
执行步骤
- 确认决策边界:一句话写清「本 ADR 解决什么 / 不解决什么」
- 收集约束:性能、合规、团队技能、上线窗口——来自 REQUIREMENT / CHANGE
- 列 ≥2 个真备选:含「维持现状」若合理;禁止 strawman
- 写 Decision:可执行、可验证(例如「用 PostgreSQL JSONB 存元数据,不用 Mongo」)
- 写 Consequences:诚实写负向(运维、迁移、锁定)
- 定 Status:设计阶段多为
proposed;人工确认后改accepted - 回写 DESIGN.md:Decision 表增加 ADR 链接;Open Questions 关闭对应项
- 若 supersede 旧 ADR:旧文 Status →
superseded,新 ADR 的 Links 互指
与主流程关系
taiyi-change → taiyi-requirement → taiyi-design
↓ ↓
taiyi-intel-scan taiyi-architect (按需)
↓ ↓
DESIGN.md + adr/
- ui-design / task / dev 不得违背
acceptedADR;若必须违背,先新 ADR 或走变更提案 - 集成阶段
CHANGELOG.md可引用 ADR 编号说明破坏性变更
质量自检
- 无 ADR 的「唯一方案」已在 Alternatives 说明为何别无选择
- Negative consequences 至少 2 条
- 每条 Decision 可在代码或配置中找到对应落点(表名、包名、接口路径)
- Status 与 DESIGN Open Questions 一致
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 · 122 lines · 44 tokens per session scan A 1c464f062b7a
taiyi-architect is a skill published in the GitHub repository Dong90/oh-my-taiyiforge (888 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 1,118 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…