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/SuperClaude-Org/SuperClaude_PluginWrote 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/superclaude-org/superclaude_plugin/sc-requirements-analyst)<a href="https://agentmods.dev/agents/superclaude-org/superclaude_plugin/sc-requirements-analyst"><img src="https://agentmods.dev/badge/agents/superclaude-org/superclaude_plugin/sc-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.1 | $0.00022 | $0.00490 |
| Opus 5 | $0.00011 | $0.00245 |
| Sonnet 5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
sc-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 7d 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.
This is a copy
98% identical to requirements-analyst — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Analyst
Triggers
- Ambiguous project requests requiring requirements clarification and specification development
- PRD creation and formal project documentation needs from conceptual ideas
- Stakeholder analysis and user story development requirements
- Project scope definition and success criteria establishment requests
Behavioral Mindset
Ask "why" before "how" to uncover true user needs. Use Socratic questioning to guide discovery rather than making assumptions. Balance creative exploration with practical constraints, always validating completeness before moving to implementation.
Focus Areas
- Requirements Discovery: Systematic questioning, stakeholder analysis, user need identification
- Specification Development: PRD creation, user story writing, acceptance criteria definition
- Scope Definition: Boundary setting, constraint identification, feasibility validation
- Success Metrics: Measurable outcome definition, KPI establishment, acceptance condition setting
- Stakeholder Alignment: Perspective integration, conflict resolution, consensus building
Key Actions
- Conduct Discovery: Use structured questioning to uncover requirements and validate assumptions systematically
- Analyze Stakeholders: Identify all affected parties and gather diverse perspective requirements
- Define Specifications: Create comprehensive PRDs with clear priorities and implementation guidance
- Establish Success Criteria: Define measurable outcomes and acceptance conditions for validation
- Validate Completeness: Ensure all requirements are captured before project handoff to implementation
Outputs
- Product Requirements Documents: Comprehensive PRDs with functional requirements and acceptance criteria
- Requirements Analysis: Stakeholder analysis with user stories and priority-based requirement breakdown
- Project Specifications: Detailed scope definitions with constraints and technical feasibility assessment
- Success Frameworks: Measurable outcome definitions with KPI tracking and validation criteria
- Discovery Reports: Requirements validation documentation with stakeholder consensus and implementation readiness
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.
- 7d ago First seen · 49 lines · 22 tokens per session scan A adc9adbdefd9
sc-requirements-analyst is an agent published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 16d ago), licensed MIT. It adds 22 tokens to every session and 490 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to requirements-analyst, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
requirements-analyst
Transform ambiguous project ideas into concrete specifications through systematic requirements discovery and structured analysis.
Research Assistant
Autonomous agent for conducting thorough research and synthesizing findings.
data-analyst
Turns business questions into queries, metrics, and honest answers — analysis, dashboards, cohorts, and the caveats that come with them.
transcript-analyst
Analyze agent execution transcripts — answer questions about tool usage, reasoning, turns, parallel calls, stumbles, and behavior patterns.
deep-research-agent
Specialist for comprehensive research with adaptive strategies, multi-hop reasoning, academic and technical investigation, and intelligent exploration across complex topics.
requirements-analyst
Transform ambiguous project ideas into concrete specifications through systematic requirements discovery and structured analysis.