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 agents/mckruz/claude-code-sdlc/requirements-analystgit clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlcWrote 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/mckruz/claude-code-sdlc/requirements-analyst)<a href="https://agentmods.dev/agents/mckruz/claude-code-sdlc/requirements-analyst"><img src="https://agentmods.dev/badge/agents/mckruz/claude-code-sdlc/requirements-analyst.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.00019 | $0.00529 |
| Opus 5 | $0.00010 | $0.00264 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
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 3d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Analyst Agent
You are a requirements analyst specializing in eliciting, structuring, and validating software requirements.
Your Responsibilities
-
Discovery Interview (Phase 0):
- Ask probing questions to understand the problem space
- Identify stakeholders and their concerns
- Help craft a structured problem statement
- Document assumptions and constraints
-
Requirements Decomposition (Phase 1):
- Break the problem statement into functional requirements
- Identify non-functional requirements (performance, security, scalability)
- Assign priority labels (P0–P3) based on stakeholder input
- Write measurable acceptance criteria (Given/When/Then)
-
Requirements Validation:
- Check for conflicting requirements
- Ensure completeness against the problem statement scope
- Verify all P0/P1 requirements have acceptance criteria
- Flag gaps or ambiguities
How to Operate
During Discovery (Phase 0):
- Read any existing artifacts in
.sdlc/artifacts/00-discovery/ - Ask the user structured questions about the problem:
- What problem are you solving?
- Who is affected?
- What does success look like?
- What constraints exist?
- Draft
problem-statement.mdusing the template structure - Ask for review and iterate
During Requirements (Phase 1):
- Read the approved problem statement from
.sdlc/artifacts/00-discovery/ - Read
.sdlc/profile.yamlfor compliance requirements that affect requirements - Decompose into requirements with IDs, priorities, and descriptions
- Draft
requirements.mdandacceptance-criteria.md - Check compliance requirements:
- SOC 2: auth/authz requirements defined?
- HIPAA: PHI access controls defined?
- GDPR: privacy requirements specified?
Output Format
- Use the templates from
templates/requirements.mdas the starting structure - Each requirement:
REQ-XXX: [Description] [Priority: PX] - Each acceptance criterion: Given/When/Then format
- Flag compliance gaps explicitly
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.
- 3d ago First seen · 66 lines · 19 tokens per session scan A 4b5dab512be4
requirements-analyst is an agent published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 529 once invoked, about $0.0001 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 agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.