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/astordu/qoderharness/test4-validation-scope-selectornpx skills add astordu/qoderharness --skill test4-validation-scope-selectorgit clone --depth 1 https://github.com/astordu/qoderharnessWrote 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/astordu/qoderharness/test4-validation-scope-selector)<a href="https://agentmods.dev/skills/astordu/qoderharness/test4-validation-scope-selector"><img src="https://agentmods.dev/badge/skills/astordu/qoderharness/test4-validation-scope-selector.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00071 | $0.00515 |
| Opus 5 | $0.00036 | $0.00258 |
| Sonnet 5 | $0.00014 | $0.00103 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
test4-validation-scope-selector 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 5d 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.
What it actually says
验证范围选择
从全量测试矩阵中选择本轮真正要验证的测试点。目标是保留全景图，同时避免一次性生成和运行过多测试。
输入
读取：
.qoder/test-matrix/<feature-id>.csv
如果没有 CSV，先调用 test3-test-matrix-builder。
输出
更新同一个 CSV，不创建新文件。
主要更新字段：
selected_for_validationactionnotes
选择策略
默认选择“最小可信验证集”：
- 优先选择 P0。
- 优先选择主路径、数据完整性、边界值、数据一致性。
- 优先选择稳定、可在 CI 中运行的层级：
Service、API。 - 只保留少量 E2E 主路径，不把所有边界都放进 E2E。
- P2 或低风险 UI 交互默认延后。
- 范围外项不进入验证，保留
selected_for_validation=N。
action 建议
generate_test：本轮要生成测试。manual_review：需要人判断。defer：延后。ignore：范围外，不纳入本功能验证。
规则
- 不要删除矩阵行，只更新标记列。
- 不要因为测试多就删掉 PRD 要求；通过
selected_for_validation=N控制本轮范围。 - 如果用户指定测试层级优先级，例如“只做 Service 和 API”，按用户要求筛选。
- 如果测试点已明显适合 E2E 但成本高，保留但标记
action=defer。
下一步
完成后提示：
下一步建议调用 test5-implementation-coverage-reviewer：
在代码生成后，用同一个 CSV 对照当前代码和已有测试，标记实现状态、测试状态、证据和后续动作。
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.
- 5d ago First seen · 63 lines · 71 tokens per session scan A bc845dd6afbb
test4-validation-scope-selector is a skill published in the GitHub repository astordu/qoderharness (23 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 515 once invoked, about $0.0004 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…