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 astordu/qoderharness --skill test1-prd-intent-extractorgit 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/test1-prd-intent-extractor)<a href="https://agentmods.dev/skills/astordu/qoderharness/test1-prd-intent-extractor"><img src="https://agentmods.dev/badge/skills/astordu/qoderharness/test1-prd-intent-extractor/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/astordu/qoderharness/test1-prd-intent-extractor"><img src="https://agentmods.dev/badge/skills/astordu/qoderharness/test1-prd-intent-extractor.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.00081 | $0.00532 |
| Opus 5.5 | $0.00032 | $0.00213 |
| Sonnet 5.5 | $0.00016 | $0.00106 |
| Haiku 4.5 | $0.00008 | $0.00053 |
Grade A, and why
test1-prd-intent-extractor 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 1mo 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
PRD 需求意图提取
从 PRD 中提取可测试的需求意图。不要写测试代码，不要生成 CSV；本 Skill 只产出结构化意图表，供下一步验收条件生成使用。
输入
读取用户指定的 PRD。若未指定，优先在 .qoder/prd/ 下选择与当前功能最匹配的 Markdown 文件。
重点读取：
- 问题陈述
- 解决方案
- 用户故事
- 实现决策
- 测试决策
- 范围外
输出格式
输出 Markdown 表格：
| intent_id | prd_source | user_intent | business_risk | verifiable_result | notes |
|---|
字段说明：
intent_id：INT-001起递增。prd_source：写明来源，例如用户故事 6、测试决策、范围外。user_intent：用户真正想完成什么。business_risk：如果这个意图没被满足，会产生什么风险。verifiable_result：系统达到什么表现才算满足意图。notes：信息不足、需代码事实校准、范围外等备注。
规则
- 以 PRD 为准，不根据代码补需求。
- 不要把“范围外”变成待测需求；只标记为范围控制项。
- 每条意图必须能追溯到 PRD 中的具体来源。
- 不要产出过多重复意图；相同用户价值可以合并。
- 如果 PRD 里已有测试决策，将其转化为意图或风险，不要直接写成测试代码。
下一步
完成后提示：
下一步建议调用 test2-acceptance-criteria-builder：
基于这份需求意图表，将每条意图转成 Given/When/Then 验收条件，为测试矩阵做准备。
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.
- 1mo ago First seen · 55 lines · 81 tokens per session scan A 1f05a25a7377
test1-prd-intent-extractor is a skill published in the GitHub repository astordu/qoderharness (38 stars, last pushed 23d ago), licensed MIT. It adds 81 tokens to every session and 532 once invoked, about $0.0003 per session on Opus 5.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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.