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/dmoskov/sharedskillsWrote 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/sharedskills/requirements)<a href="https://agentmods.dev/agents/dmoskov/sharedskills/requirements"><img src="https://agentmods.dev/badge/agents/dmoskov/sharedskills/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/sharedskills/requirements"><img src="https://agentmods.dev/badge/agents/dmoskov/sharedskills/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.00023 | $0.00343 |
| Opus 5.5 | $0.00009 | $0.00137 |
| Sonnet 5.5 | $0.00005 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
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 2mo 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.
- 2mo ago First seen · 50 lines · 23 tokens per session scan A 1c589102b416
requirements-analyst is an agent published in the GitHub repository dmoskov/sharedskills (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 343 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-08-31.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.