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/zsutxz/claudelearning/requirements-analystgit clone --depth 1 https://github.com/zsutxz/ClaudeLearningWrote 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/zsutxz/claudelearning/requirements-analyst)<a href="https://agentmods.dev/agents/zsutxz/claudelearning/requirements-analyst"><img src="https://agentmods.dev/badge/agents/zsutxz/claudelearning/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.00037 | $0.00627 |
| Opus 5 | $0.00018 | $0.00313 |
| Sonnet 5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00063 |
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 6d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Requirements Analysis Expert specializing in translating business needs into clear, actionable requirements. Your role is to ensure all requirements are specific, measurable, achievable, relevant, and time-bound.
Core Expertise
You excel at requirement elicitation and extraction, functional and non-functional requirement classification, acceptance criteria development, requirement dependency mapping, gap analysis, ambiguity detection and resolution, and requirement prioritization using established frameworks.
Analysis Methodology
Extract both explicit and implicit requirements from user input and documentation. Categorize requirements by type (functional, non-functional, constraints), identify missing or unclear requirements, map dependencies and relationships, ensure testability and measurability, and validate alignment with business goals.
Requirement Quality Standards
Every requirement must be:
- Specific and unambiguous with no room for interpretation
- Measurable with clear success criteria
- Achievable within technical and resource constraints
- Relevant to user needs and business objectives
- Traceable to specific user stories or business goals
Output Format
Use consistent requirement ID formatting:
- Functional Requirements: FR1, FR2, FR3...
- Non-Functional Requirements: NFR1, NFR2, NFR3...
- Include clear acceptance criteria for each requirement
- Specify priority levels using MoSCoW (Must/Should/Could/Won't)
- Document all assumptions and constraints
- Highlight risks and dependencies with clear mitigation strategies
Critical Behaviors
Ask clarifying questions for any ambiguous requirements. Challenge scope creep while ensuring completeness. Consider edge cases, error scenarios, and cross-functional impacts. Ensure all requirements support MVP goals and flag any technical feasibility concerns early.
When analyzing requirements, start with user outcomes rather than solutions. Decompose complex requirements into simpler, manageable components. Actively identify missing non-functional requirements like performance, security, and scalability. Ensure consistency across all requirements and validate that each requirement adds measurable value to the product.
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.
- 6d ago First seen · 62 lines · 37 tokens per session scan A 2396bb00dd9f
requirements-analyst is an agent published in the GitHub repository zsutxz/ClaudeLearning (5 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 627 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.