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 agentmods add skills/lync-cyber/cataforge/testingnpx skills add lync-cyber/CataForge --skill testinggit clone --depth 1 https://github.com/lync-cyber/CataForgeWhat 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 | $0.00092 | $0.01992 |
| Opus 5 | $0.00046 | $0.00996 |
| Sonnet 5 | $0.00018 | $0.00398 |
| Haiku 4.5 | $0.00009 | $0.00199 |
Grade A, and why
testing 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 2d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
测试 (testing)
能力边界
- 能做: 测试策略规划、测试用例矩阵编写、Unit/Integration/E2E测试编写与执行、覆盖率分析、缺陷记录
- 不做: 源代码修改 / 缺陷修复(由 debug 负责，testing 仅编写测试)、架构变更
与tdd-engine的关系
- tdd-engine(Phase 5): 开发阶段，为每个任务卡编写RED测试+GREEN实现，产出单元测试
- testing(Phase 6): 测试阶段，补充集成测试/E2E测试、审查tdd-engine测试覆盖盲区、产出测试报告
- 两者独立运行，无依赖关系
- testing不重写tdd-engine已有测试，仅补充覆盖盲区(边界条件、异常路径、未覆盖分支)
与debug的关系
- testing 输出"缺陷清单"后，由 orchestrator 调度 debug skill 接管根因定位与最小修复
- debug 修复完成后由 testing 重跑相关用例验证；debug 内部已含回归验证步骤，testing 在缺陷清单上标 closed
- testing 仅记录现象 / 复现步骤 / 关联任务 ID
输入规范
- dev-plan 任务列表和验收标准
- arch 接口契约
- ui-spec 交互流程(E2E测试时)
- 已有代码和单元测试(DEV阶段产出)
输出规范
- 测试策略(金字塔分层 + 覆盖率目标)
- 测试用例矩阵(TC-{NNN})
- 测试文件(单元/集成/E2E)
- 测试执行报告
- 缺陷清单(关联T-{NNN})
操作指令
指令1: 规划测试策略 (plan)
- 分析dev-plan任务和arch接口，评估测试范围
- 规划测试金字塔分层(Unit/Integration/E2E占比)
- 编写测试用例矩阵(TC-{NNN})，与AC一一映射
- 设定覆盖率目标(按模块)
- 确定测试环境和工具链配置
指令2: 编写测试 (write)
语言细则: 根据
framework.jsonproject.languages，按需载入本 skillreferences/lang-<lang>.md（仅 active 语言，逐个 Read），获取对应语言的测试编写细则（框架与工具栈、断言风格、fixture/setup、参数化、mock/stub、命名分层）。
按测试类型编写:
Unit测试:
- 输入: 任务卡验收标准 + 接口契约
- 范围: 仅补充 tdd-engine 未覆盖的函数/方法级盲区（边界条件 / 异常路径 / 未覆盖分支），隔离外部依赖，不重写已有单测
- 工具: 按项目技术栈选择单测框架
Integration测试:
- 输入: arch接口契约 + 模块间依赖关系
- 范围: 模块间接口调用、数据流转
- 重点: API契约验证、数据库交互、IPC边界
E2E测试:
- 输入: ui-spec交互流程 + 核心用户路径
- 范围: 完整用户场景，端到端验证
- 工具: 按项目选择 e2e 框架（各框架真实输入 API 见
test-and-e2e-apis.md）
指令3: 执行测试 (execute)
- 运行全部测试套件(或指定类型)
- 收集测试结果和覆盖率数据
- 记录失败用例和缺陷，关联任务ID(T-{NNN})
- 缺陷即时归档，包含复现步骤和上下文
指令4: 产出报告 (report)
- 汇总测试执行结果(通过/失败/跳过)
- 覆盖率分析(对比目标)
- 缺陷清单(严重等级 + 关联任务)
- 结论与建议(是否达到发布标准)
- 经 context authoring（
write-doc/write-narrative/transact）填充 test-report，再cataforge context finalize导出人审视图
Layer 1 检查项
权威清单见
cataforge.runtime.skill.builtins.testing.CHECKS_MANIFEST（framework-review 自动对账，本段与 manifest 不一致即 FAIL）。
- e2e 后门正则扫描 (tests/e2e/**) — 覆盖语言/扩展名由 e2e-{lang}.yaml 声明；命中后门注入模式（预构造状态直注入 / 测试专用查询参数 / store 直灌等，按语言正则见 e2e-{lang}.yaml）即 WARN
- 真实输入路径声明 — e2e 套件至少含一处真实交互调用（键入 / 填充 / 点击，各框架 API 见
test-and-e2e-apis.md），无任何 → WARN（提示套件可能纯 fixture 注入）
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 118 lines · 92 tokens per session scan A dbd5923f9def
testing is a skill published in the GitHub repository lync-cyber/CataForge (128 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,992 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.