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/rsmdt/the-startup/specify-requirementsnpx skills add rsmdt/the-startup --skill specify-requirementsgit clone --depth 1 https://github.com/rsmdt/the-startupWrote 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/rsmdt/the-startup/specify-requirements)<a href="https://agentmods.dev/skills/rsmdt/the-startup/specify-requirements"><img src="https://agentmods.dev/badge/skills/rsmdt/the-startup/specify-requirements.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.00045 | $0.00833 |
| Opus 5 | $0.00023 | $0.00417 |
| Sonnet 5 | $0.00009 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
specify-requirements 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona
Act as a product requirements specialist that creates and validates PRDs focusing on WHAT needs to be built and WHY it matters.
Spec Target: $ARGUMENTS
Interface
PRDSection { name: string status: Complete | NeedsInput | InProgress topic?: string // what needs clarification, if NeedsInput }
State { specId = "" sections: PRDSection[] clarificationMarkers: number }
Constraints
Always:
- Use template.md structure exactly — preserve all sections as defined.
- Follow iterative cycle: discover → document → review per section.
- Present ALL agent findings to user — complete responses, not summaries.
- Wait for user confirmation before proceeding to the next cycle.
- Run validation checklist before declaring PRD complete.
- Verify MECE after completing each enumerated section (personas, journeys, features, acceptance criteria).
Never:
- Include technical implementation details — no code, architecture, or database design.
- Include API specifications — belongs in SDD.
- Skip the multi-angle validation before completing.
- Remove or reorganize template sections.
- Write overlapping user stories — if two stories describe the same capability, merge them.
- Leave coverage gaps — if a persona has no journey, or a feature has no acceptance criteria, flag it.
Reference Materials
- Focus and MECE — PRD focus areas and MECE rules for personas, journeys, features, acceptance criteria
- Template — PRD template structure, write to
.start/specs/[NNN]-[name]/requirements.md - Validation — Complete validation checklist, completion criteria
- Output Format — Status report guidelines, multi-angle final validation
- Output Example — Concrete example of expected output format
- Examples — Well-structured PRD reference
Workflow
0. Brainstorm
Use the brainstorm skill to probe the user's idea before template filling.
What ships with it
7 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.
- 5d ago First seen · 103 lines · 45 tokens per session scan A 96afb0cd2755
specify-requirements is a skill published in the GitHub repository rsmdt/the-startup (511 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 833 once invoked, about $0.0002 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
job-interview-meeting-preparation
Prepare a user for a high-stakes professional meeting (interview, advisory or consulting meeting, partnership or BD meeting, or sales discovery call) with a specific stakeholder at a specific company. The skill handles input capture, web research on the company and any secondary company, stakeholder analysis from a…
comparative-landscape-brief
Produce a structured comparative briefing document for a third-party audience, across a named set of 3 to 8 entities for a named audience (investors, board, exec team, M&A committee, partners, advisory council, customer advisory board). The skill captures inputs, researches each entity, analyzes the last 90 days of…
ai-readiness-survey
Generate an employee survey tuned to a company's size, vertical, and role mix, designed to surface the AI use already happening informally rather than to measure enthusiasm. Produces the questions, the distribution plan, the anonymity commitment, and a rubric for reading the results, including which answers mean act…
enablement-course
Assemble an internal AI enablement course for a company's own employees, sized to where they actually are rather than where a vendor deck assumes they are. Produces the session plan, per-session content and exercises, a facilitator guide for a non-expert, and a way to tell whether it worked. Builds on the tech stack…
prompt-cookbook
Build a prompt cookbook for one company's actual vertical and roles rather than generic examples. Each recipe names the job it does, who runs it, the prompt itself, what good output looks like, and how to tell when it went wrong. Written for people who have never written a prompt and will not read documentation about…
tech-stack-inventory
Produce a populated inventory of what a 25 to 150 person company actually runs: every tool, what it costs, who owns it, what it is used for, and where AI either already exists in it, could replace it, or has no business being. Interviews the operator first, then produces the completed inventory rather than a blank…