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-testgit 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-test)<a href="https://agentmods.dev/skills/dong90/oh-my-taiyiforge/taiyi-test"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-test/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-test"><img src="https://agentmods.dev/badge/skills/dong90/oh-my-taiyiforge/taiyi-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 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 186 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 153 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 156 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 159 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.00024 | $0.02351 |
| Opus 5 | $0.00012 | $0.01175 |
| Sonnet 5 | $0.00005 | $0.00470 |
| Haiku 4.5 | $0.00002 | $0.00235 |
Grade A, and why
taiyi-test 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taiyi-test — 测试验证
进入本阶段前请优先读
.taiyi/changes/<slug>/PHASE-CONTEXT.md（~500 tokens），不要全量加载上游工件。
框架集成
本阶段使用以下框架：
| 框架 | 用途 | 何时加载 |
|---|---|---|
| Harness | 阶段门禁与推进（status → continue；legacy：npx taiyi complete） |
全程 |
| GStack | browse — 用于 E2E 浏览器测试和截图验证 |
Round 5（E2E 轮） |
| Superpowers | verification-before-completion — 完成前全量验证 |
完成前 |
OpenSpec / Spec-Kit / OMO 在本阶段不涉及。
前置门禁（Pre-flight）
0.1 上游确认
- dev 阶段已过关（
.taiyi/changes/<slug>/.dev-complete存在且exitCode: 0） - 实现代码已通过 TDD 红→绿循环
0.2 Profile 判定
| Profile | TEST.md 要求 |
|---|---|
full |
完整覆盖：5 rounds + 6 维回归测试 + 新 file GREP 填空 + Traceability |
api/ui |
同 full |
lite |
简化版：跳过 round 4-5，6 维回归可选 |
spike/micro |
跳过本阶段 |
nano |
跳过 |
0.3 前置检查清单
- .dev-complete 存在且有 GREEN 证据
- 明确项目的测试命令（npm test / pytest / cargo test 等）
步骤
工件契约
| 层 | 路径 | 职责 |
|---|---|---|
| 语义真源 | test.json |
Zod（src/schemas/test.ts） |
| 生成视图 | TEST.md |
hbs（src/templates/test.hbs） |
| 流程 | 本 Skill | 5 轮 AC 覆盖、6 维回归、Traceability |
工作流：实跑测试 → 更新 json 证据 → scripts/taiyi-forge.sh render <slug> test → status → continue。
详见 docs/taiyi/artifact-contract.md。
json 字段（Zod 摘要）
| 字段 | 要求 |
|---|---|
title |
测试计划标题 |
test_plan |
≥1 用例；id / description / status（passed/failed/pending） |
unit_framework / unit_coverage_target |
可选 |
edge_cases / performance_tests / security_checks |
可选 |
regression_plan / regression_items |
可选；6 维回归仪表盘内容 |
mocking_boundaries |
可选；哪些层可 mock |
summary / coverage |
可选；执行摘要 |
evidence |
有 passed 时推荐填真跑命令 |
写作指引（填入 json，render 生成 TEST.md）
1. TEST.md 全局结构
# TEST: <slug 标题>
## Overview
| AC | Round | Type | Status |
|----|-------|------|--------|
2. 按 AC 的 5 轮测试
每轮一个 table，AC 编号来自 REQUIREMENT.md：
### Round 1: 功能正确性（AC 正向）
| AC | PR | Test | Priority | Key Assertions |
|----|----|------|----------|----------------|
### Round 2: 边界条件（AC 负面 + 边值）
| AC | PR | Test | Priority | 边界值 |
|----|----|------|----------|--------|
### Round 3: 错误处理（AC 异常路径）
| AC | PR | Test | Priority | Error Handling |
|----|----|------|----------|---------------|
### Round 4: 集成（跨组件）
| AC | PR | Test | Priority | Endpoint / Interaction |
|----|----|------|----------|-----------------------|
### Round 5: 端到端（关键路径 / 用户流程）
| AC | PR | Test | Priority | Flow |
|----|----|------|----------|------|
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 · 235 lines · 24 tokens per session scan A 59b64eed9246
taiyi-test is a skill published in the GitHub repository Dong90/oh-my-taiyiforge (888 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 2,351 once invoked, about $0.0001 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
colony-dogfood
Conduz um experimento de dogfood onde a colônia Pi executa uma task do .project/tasks.json em dois tempos (research → código) com gates do operador. Use quando o operador quiser ativar um experimento colony-experiment-phase1 ou colony-experiment-phase2.
create-pi-web-extension
Como criar/extender extensões web no pi com arquitetura determinística, segurança mínima e testes automatizados (smoke + e2e via pi-test-harness).
test-pi-extension
Como testar extensões pi com @marcfargas/pi-test-harness. Use quando o usuário quiser testar uma extensão, criar testes automatizados, ou validar que um pacote pi funciona após publish.
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.