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 RealDougEubanks/ClaudeMarketplace --skill requirements-generatorgit clone --depth 1 https://github.com/RealDougEubanks/ClaudeMarketplaceWrote 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/realdougeubanks/claudemarketplace/requirements-generator)<a href="https://agentmods.dev/skills/realdougeubanks/claudemarketplace/requirements-generator"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/requirements-generator/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/realdougeubanks/claudemarketplace/requirements-generator"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/requirements-generator.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.00031 | $0.01714 |
| Opus 5 | $0.00015 | $0.00857 |
| Sonnet 5 | $0.00006 | $0.00343 |
| Haiku 4.5 | $0.00003 | $0.00171 |
Grade A, and why
requirements-generator 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 11d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Generator
Take a project idea, feature description, or user story and generate a structured requirements document with functional requirements, non-functional requirements, Gherkin acceptance criteria, edge cases, and out-of-scope items.
Instructions
Two modes:
- Description mode (default): user provides a free-form description or pastes a Jira/Confluence URL. Claude generates requirements from that.
- Interview mode (
/requirements-generator --interview): Claude asks a structured set of questions one at a time, then generates requirements from the answers.
-
Gather input. Ask the user what they want to build if no description has been provided. Accept any of:
- A pasted feature description or user story
- A Jira ticket URL or Confluence page URL (read via available MCP tools if present)
- A brief verbal description of the feature
Prompt: "Describe the feature or system you want to build. Include the user need it addresses and any known constraints."
If the user invoked with
--interview, skip this prompt and proceed to the Interview Mode section below instead. -
Understand the existing codebase (if one exists). Use Glob on
*to detect the project structure. Readpackage.json,pyproject.toml, orgo.modto identify the tech stack. Read 3–5 representative files fromsrc/orapp/— entry points first (index.*,main.*,app.*), then one route/handler file and one model/schema file — to understand patterns and conventions. Do not read the whole source tree. This ensures requirements fit what already exists. -
Check for existing requirements. Use Glob on
docs/requirements/**/*.md. If matching files exist, read them to avoid duplicating requirements already captured. Note any related requirements in the new document. -
Determine the feature name. Derive a kebab-case feature name from the description (e.g., "user authentication" →
user-authentication). This becomes the output filename.
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.
- 11d ago First seen · 190 lines · 31 tokens per session scan A a6cc323b095d
requirements-generator is a skill published in the GitHub repository RealDougEubanks/ClaudeMarketplace (1 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,714 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-31.
Other skills, from other repositories
tools-unity-test-framework
Unity Test Framework patterns for EditMode and PlayMode tests including async testing, mocking, and test organization.
plan-qa
Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA- - .md) that /execute-qa…
execute-qa
Executes a QA specification (specs/qa/QA- - .md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact…
generate-tasks
Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS- - .md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
smoke-check
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.