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-restylegit 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-restyle)<a href="https://agentmods.dev/skills/dong90/oh-my-taiyiforge/taiyi-restyle"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-restyle/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-restyle"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-restyle.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.01277 |
| Opus 5 | $0.00019 | $0.00639 |
| Sonnet 5 | $0.00008 | $0.00255 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
taiyi-restyle 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taiyi-restyle
目的
当 UI-DESIGN.md 要求视觉层大面积改版(token、间距、组件皮肤)时,把 work 拆成可独立 PR 的清单,避免塞进单个 dev slice 导致 review 不可审、回滚困难。
何时使用
| 信号 | 建议 |
|---|---|
taiyi_assess 因 hasUi 推荐 |
考虑本 Skill |
| UI-DESIGN 含「改版 / 换肤 / 设计系统迁移」 | 必用 |
| 单组件颜色微调 | 否,留在 TASK 一条 |
| 无 UI(纯 API) | 跳过 |
输入
UI-DESIGN.md、DESIGN.md(前端边界)TASK.md(避免重复编号)- 设计 token / Figma 链接 / 截图(若有)
- (可选)
CONTEXT.md中的前端目录约定
输出
.taiyi/changes/<slug>/ui-restyle-tasks.md- 可选:每项对应 截图基线路径
.taiyi/changes/<slug>/screenshots/before/
任务拆分原则
- 按用户旅程切片,非按 CSS 文件:「登录页」「设置抽屉」优于「改 button.css」
- 每项 ≤1 天 量级;更大则再拆
- 每项须 可独立合并(feature flag 或隔离路由若需要,写在任务里)
- 先 token / 基础组件,后 页面组合(减连锁冲突)
- 无障碍与响应式为验收硬条件,不是可选 follow-up
任务清单格式
# UI Restyle Tasks: <slug>
> 来源:UI-DESIGN.md §… · 与 TASK.md 关系:补充视觉层,不替代功能任务
## Token / 基础层
| ID | 范围 | 变更 | 依赖 | 验收 |
|----|------|------|------|------|
| R1 | `styles/tokens.css` | 色板 v2 | — | 无回归 snapshot |
| R2 | `Button` 组件 | 圆角/阴影 | R1 | Storybook / 截图 |
## 页面层
| ID | 页面/流程 | 变更 | 依赖 | 验收 |
|----|-----------|------|------|------|
| R10 | `/settings` | 密度与侧栏 | R1,R2 | 桌面+移动截图 |
## 无障碍(横切)
| ID | 项 | 验收 |
|----|-----|------|
| A1 | 对比度 WCAG AA | axe / 手动表 |
| A2 | 焦点环可见 | 键盘录屏或截图 |
执行步骤
- 读 UI-DESIGN:提取 Components、States、Breakpoints、A11y 四块需求
- 盘点影响面:路由 → 页面组件 → 共享组件 → token(自下而上列表)
- 建依赖图:R2 依赖 R1;页面依赖基础组件——在表中填「依赖」列
- 写验收:每项必须 可证据化:
- 截图对比(before/after 同视口)
- 或设计工具标注一致
- 或
data-testid+ 视觉回归(若项目有)
- 与 TASK.md 对齐:
- 功能任务 ID(T3)与视觉任务 ID(R10)交叉引用
- 同一文件同时改逻辑+皮肤 → 拆两 PR 或标明顺序
- dev 执行:每个 R* 对应
taiyi-dev一切片或子 PR;完成在 TASK 或 CHANGELOG 勾 ID
与主流程
taiyi-ui-design → taiyi-task
↓
taiyi-restyle(大改版时)
↓
taiyi-dev(按 R1,R2,… 切片)
↓
taiyi-test(含视觉/a11y 证据)
taiyi-test:至少一条用例覆盖 横切 A* 清单taiyi-review:对照 ui-restyle-tasks 勾完成情况;缺截图 → Request changes
质量自检
- 每项有 明确验收,无「好看即可」
- 引用
UI-DESIGN.md章节号或组件名 - 移动端与桌面若 UI-DESIGN 有要求,任务表分别列验收
- 未引入未在 UI-DESIGN 出现的 scope(新页面须回 requirement)
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 · 116 lines · 39 tokens per session scan A 8cda797073d2
taiyi-restyle 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 1,277 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
create-pi-theme
Como criar um tema visual para o TUI do pi. Use quando o usuário quiser personalizar cores e aparência do terminal.
visual-design
A design skill for turning content into complete, self-contained HTML pages and visual materials such as websites, banners, posters, reports, resumes, and portfolios. It follows a defined visual design system and does not use outside images or code libraries.
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…
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-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…