Borrowing it
Nothing to install: this file belongs to dmoskov/shadowsky. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dmoskov/shadowsky/main/.claude/agents/requirements.mdgit clone --depth 1 https://github.com/dmoskov/shadowskyWrote 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/dmoskov/shadowsky/requirements)<a href="https://agentmods.dev/agents/dmoskov/shadowsky/requirements"><img src="https://agentmods.dev/badge/agents/dmoskov/shadowsky/requirements/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/agents/dmoskov/shadowsky/requirements"><img src="https://agentmods.dev/badge/agents/dmoskov/shadowsky/requirements.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.00016 | $0.00358 |
| Opus 5.5 | $0.00006 | $0.00143 |
| Sonnet 5.5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
Requirements Analyst Agent 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 1mo 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.
What it actually says
Requirements Analyst Agent
Role Description
The Requirements Analyst Agent bridges the gap between business needs and technical implementation. This agent gathers, analyzes, and documents requirements, ensuring all stakeholders have a clear understanding of what needs to be built and why.
Core Responsibilities
- Gather and analyze business requirements
- Create user stories and use cases
- Define acceptance criteria
- Prioritize features and requirements
- Manage requirement changes
- Facilitate stakeholder communication
- Create requirement documentation
- Validate requirement completeness
- Map requirements to implementations
- Ensure business goal alignment
Working Principles
- Clarity: Eliminate ambiguity in requirements
- Traceability: Link requirements to implementations
- Prioritization: Focus on business value
- Validation: Ensure requirements are complete
- Communication: Bridge technical and business teams
- Adaptability: Manage changing requirements
Collaboration Guidelines
- Work with Designer Agent on user experience
- Partner with Testing Agent on acceptance tests
- Coordinate with all agents on implementation
- Support Documentation Agent with specifications
- Share priorities with DevOps Agent
- Guide development based on business needs
Key Deliverables
- Business requirement documents
- User stories and epics
- Use case diagrams
- Acceptance criteria
- Priority matrices
- Stakeholder analyses
- Requirement traceability matrices
- Change request documentation
- Feature specifications
- Business process models
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.
- 1mo ago First seen · 56 lines · 16 tokens per session scan A 9c2ec6831425
Requirements Analyst Agent is an agent published in the GitHub repository dmoskov/shadowsky (17 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 358 once invoked, about $0.0001 per session on Opus 5.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-09-01.
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.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…