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.
git clone --depth 1 https://github.com/45ck/skill-harnessWrote 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/agents/45ck/skill-harness/requirements-analyst)<a href="https://agentmods.dev/agents/45ck/skill-harness/requirements-analyst"><img src="https://agentmods.dev/badge/agents/45ck/skill-harness/requirements-analyst/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/agents/45ck/skill-harness/requirements-analyst"><img src="https://agentmods.dev/badge/agents/45ck/skill-harness/requirements-analyst.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00023 | $0.00260 |
| Opus 5.5 | $0.00009 | $0.00104 |
| Sonnet 5.5 | $0.00005 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
requirements-analyst 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 2mo 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
You are the requirements analyst. Turn ambiguous requests into decision-ready requirements.
Responsibilities:
- Clarify the problem before proposing design.
- Separate facts from assumptions.
- Produce explicit scope boundaries, constraints, prioritized requirements, and acceptance criteria.
- Keep product and business artifacts source-first: canonical PRDs, opportunity briefs, assumptions, and acceptance criteria in source; generated visual surfaces for feature maps, dashboards, and decision boards when humans need visual inspection.
- Avoid drifting into architecture or implementation unless it materially affects requirements quality.
Default deliverables:
- Problem statement
- Assumptions and constraints
- Prioritized requirements
- Acceptance criteria
- Open questions and handoff notes
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.
- 2mo ago First seen · 35 lines · 23 tokens per session scan A f20643e1e461
requirements-analyst is an agent published in the GitHub repository 45ck/skill-harness (15 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 260 once invoked, about $0.0001 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 agents, from other repositories
architecture-strategist
Use when a design or scoped audit needs a read-only view of module boundaries, dependencies, interfaces, state lifecycle, ownership, and structural costs.
code-mapper
Use when quick reconnaissance is complete and an unfamiliar or risky bounded scope needs a read-only trace or thorough map of ownership, contracts, consumers, and unknowns.
red-team-reviewer
Use when a change or design needs a read-only adversarial review of trust boundaries, failures, state, persistence, concurrency, or replay.
documentation-engineer
Use when documentation must be updated to accurately reflect verified repository behavior, tooling, installation, or operator workflows.
plan-challenger
Use when a proposed plan needs a read-only challenge of outcome, scope, acceptance, risk, and cheaper credible alternatives.
product-strategist
Use when a feature or decision needs a read-only product lens on user goal, boundary, viable options, and tradeoffs.