Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sd0xdev/sd0x-harnessnpx agentmods add skills/sd0xdev/sd0x-harness/req-analyzeWrote 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/sd0xdev/sd0x-harness/req-analyze)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/req-analyze"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/req-analyze/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/sd0xdev/sd0x-harness/req-analyze"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/req-analyze.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.00101 | $0.03966 |
| Opus 5.5 | $0.00040 | $0.01586 |
| Sonnet 5.5 | $0.00020 | $0.00793 |
| Haiku 4.5 | $0.00010 | $0.00397 |
Grade A, and why
req-analyze 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.
How it starts
The opening of the file, as written. The whole thing — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Analysis Skill
Trigger
- Keywords: requirements analysis, analyze requirements, decompose requirements, stakeholder analysis, 需求分析, requirement decomposition, analyze needs
When NOT to Use
- Solution comparison / feasibility evaluation (use
/feasibility-study) - Technical specification writing (use
/tech-spec) - Per-task tracking tickets (use
/create-request— requests are date-prefixed non-lifecycle docs for progress tracking, not feature-level requirements docs; see Relationship section below) - Issue root cause analysis (use
/issue-analyze) - Architecture design (use
/architecture) - Implementation (use
/feature-dev)
Boundary Contract
/req-analyze is problem-space only:
- Defines problems, analyzes stakeholders, decomposes requirements, prioritizes needs
- Must NOT rank solutions, estimate implementation effort, or produce feasibility recommendations
- Solution-space concerns discovered during analysis → log as Open Questions with suggestion to run
/feasibility-study
Relationship with /create-request
1-requirements.md is a lifecycle document, not a task ticket. They live in different document classes per @rules/docs-numbering.md and serve different audiences.
| Dimension | /req-analyze → 1-requirements.md |
/create-request → requests/YYYY-MM-DD-*.md |
|---|---|---|
| Doc class | Lifecycle (Phase 1, numeric prefix) | Request ticket (date-prefixed, non-lifecycle — per @rules/docs-numbering.md) |
| Count per feature | One (upsert / incremental refine) | Many (one per task) |
| Position in workflow | Before /tech-spec (design phase) |
After /tech-spec (execution phase) |
| Content focus | Problem space — 5-Why, FR/NFR, MoSCoW, stakeholders | Execution — Status, Progress, AC checklist, Related Files |
| Granularity | Feature-wide | Single task (AC ≤ 8) |
| Update pattern | Document upsert | Status tracking (scan / update / update-all / --verify-ac) |
| Audience | Designers, decision-makers | Executors, progress trackers |
What ships with it
3 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.
- 1mo ago Changed 38891738d6a1
- 1mo ago First seen · 378 lines · 101 tokens per session scan A 237225dbbeff
req-analyze is a skill published in the GitHub repository sd0xdev/sd0x-harness (194 stars, last pushed 16d ago), licensed MIT. It adds 101 tokens to every session and 3,966 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
comet-classic
A Chinese-language workflow guide for starting or resuming a structured software change using OpenSpec and Superpowers.
comet-native
A workflow for managing Native changes in Comet, where requirements, progress, and acceptance results are saved in project files. It uses the Comet command-line runtime to move through defined work stages.
comet-build
A Comet workflow step for turning an approved design into an implementation plan and completed code changes. Comet is the project workflow system described by the add-on.
grill-test
An end-to-end test workflow that runs a sequence of planning and implementation skills through real user confirmations and tests. It covers grilling an idea, writing a specification, creating tickets, implementing them, and reviewing the result.
comet-github-idea-to-issue
A workflow for turning a local idea, bug observation, or improvement proposal into a focused GitHub Issue draft. GitHub Issues are shared records for bugs, features, questions, and maintenance work.
exploration
Two-mode exploration skill: (1) design dialogue — turn rough ideas into validated designs through collaborative interview before planning; (2) spike — throwaway code answering ONE design question, deleted or absorbed, never shipped. Router invokes mode via dispatch context.