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-evolvegit 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-evolve)<a href="https://agentmods.dev/skills/dong90/oh-my-taiyiforge/taiyi-evolve"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-evolve/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-evolve"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-evolve.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.00037 | $0.01249 |
| Opus 5 | $0.00018 | $0.00624 |
| Sonnet 5 | $0.00007 | $0.00250 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade A, and why
taiyi-evolve 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 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.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taiyi-evolve
目的
dev / test 完成后，对齐设计与现实：防止「代码已是真相、文档仍是幻想」，并为 integration 与后续维护留下可追溯 diff 说明。
何时使用
| 信号 | 动作 |
|---|---|
实现偏离 DESIGN.md 架构图或模块边界 |
必跑 |
| 多 dev slice 合并，DESIGN 未更新 | 必跑 |
taiyi_assess = high |
建议在 test 后、review 前 |
| 实现与 DESIGN 完全一致 | 可写一行「无漂移」归档 |
输入
DESIGN.md、TASK.md、CHANGELOG草稿（若有）- 实际代码树（
git diff相对 design 冻结点或main...HEAD） - （可选）
adr/、CONTEXT.md - （可选）
taiyi-health报告——辅助判断「漂移是否引入质量退化」
输出
.taiyi/changes/<slug>/architecture-sync.md- 提议的
DESIGN.md补丁（可直接编辑或附 unified diff） - 若决策级变化：触发
taiyi-architect新 ADR（Status: accepted / superseded）
执行步骤
1. 建立对比基线
- 标定「设计意图来源」：
DESIGN.md版本（commit 或日期） git diff --stat+ 重点路径列表（与 DESIGN Architecture 节交叉）- 列出 新增 / 删除 / 移动 的模块（表格式）
2. 漂移分类
| 类型 | 定义 | 处理 |
|---|---|---|
| Cosmetic | 命名、文件位置，行为不变 | 更新 DESIGN 图示即可 |
| Structural | 新组件、边界变化、依赖反转 | 更新 DESIGN + 考虑 ADR |
| Behavioral | 对外契约、错误码、性能特征变 | 更新 REQUIREMENT 追溯 + ADR |
| Expedient | 临时 workaround，已知技术债 | TASK 记债 + DESIGN Open Questions |
3. 逐节对账
对 DESIGN.md 每个主章节填：
- 仍准确 ✓
- 已过时 ✗ + 实际现状一句话
- 建议补丁（粘贴可合并段落）
4. 决策升级判断
若漂移涉及以下任一项 → 必须 taiyi-architect：
- 存储 / 鉴权 / 公开 API 形状
- 删除 ADR 曾接受的方案
- 引入新上游依赖（网络、许可证、运维）
5. 输出 architecture-sync.md
写入 Summary、漂移表、补丁、开放债项；文末 Gate：
- DESIGN 已更新或明确「无需更新」理由
- 新 ADR 已建（若需要）
- TASK 未完成任务已关闭或转新 slug
6. 与 integration 衔接
CHANGELOG.md 可引用 architecture-sync 的 用户可见行为变化；taiyi_sync_openspec 前确保 design.md 与 DESIGN 一致。
architecture-sync.md 模板
# Architecture Sync: <slug>
## Baseline
- DESIGN 基线：…
- 代码范围：`main...HEAD`（N files）
## Drift Summary
| 类型 | 区域 | 设计说 | 实现是 | 处理 |
|------|------|--------|--------|------|
| Structural | auth | session | JWT | ADR-0004 + 补丁 §3 |
## DESIGN.md 对账
### Architecture
- 仍准确：…
- 已过时：…
- 补丁：
\`\`\`markdown
（可粘贴进 DESIGN 的段落）
\`\`\`
## 技术债 / Open Items
- [ ] …
## Gate
- [x] DESIGN 已更新
- [x] ADR-0004 accepted
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 · 144 lines · 37 tokens per session scan A 8cab973f3ee4
taiyi-evolve is a skill published in the GitHub repository Dong90/oh-my-taiyiforge (888 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 1,249 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…
create-issue
Transitional alias — prefer /prflow:specs, which runs the same issue-drafting pipeline. Use when a rough user story, bug report, feature idea, piece of feedback, or an implementation plan should be recorded as a GitHub issue rather than built right now. This command name is retained so existing /prflow:create-issue…
neurolink-guide
Guide for using the NeuroLink SDK and CLI. Invoke when users ask how to use neurolink, integrate AI providers, add MCP tools, configure RAG, set up memory, deploy servers, or work with multimodal content. Covers SDK, CLI, providers, tools, and enterprise features.
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…