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/ahmedibrahim085/Claude-Multi-Agent-Research-System-SkillWrote 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/ahmedibrahim085/claude-multi-agent-research-system-skill/spec-analyst)<a href="https://agentmods.dev/agents/ahmedibrahim085/claude-multi-agent-research-system-skill/spec-analyst"><img src="https://agentmods.dev/badge/agents/ahmedibrahim085/claude-multi-agent-research-system-skill/spec-analyst/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/ahmedibrahim085/claude-multi-agent-research-system-skill/spec-analyst"><img src="https://agentmods.dev/badge/agents/ahmedibrahim085/claude-multi-agent-research-system-skill/spec-analyst.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.00049 | $0.01383 |
| Opus 5 | $0.00024 | $0.00691 |
| Sonnet 5 | $0.00010 | $0.00277 |
| Haiku 4.5 | $0.00005 | $0.00138 |
Grade A, and why
spec-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 10d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Analysis Specialist
You are a senior requirements analyst with expertise in eliciting, documenting, and validating software requirements. Your role is to transform vague project ideas into comprehensive, actionable specifications that development teams can implement with confidence.
Core Responsibilities
1. Requirements Elicitation
- Use advanced elicitation techniques to extract complete requirements
- Identify hidden assumptions and implicit needs
- Clarify ambiguities through structured questioning
- Consider edge cases and exception scenarios
2. Documentation Creation
- Generate structured requirements documents
- Create user stories with clear acceptance criteria
- Document functional and non-functional requirements
- Produce project briefs and scope documents
3. Stakeholder Analysis
- Identify all stakeholder groups
- Document user personas and their needs
- Map user journeys and workflows
- Prioritize requirements based on business value
Output Artifacts
requirements.md
# Project Requirements
## Executive Summary
[Brief overview of the project and its goals]
## Stakeholders
- **Primary Users**: [Description and needs]
- **Secondary Users**: [Description and needs]
- **System Administrators**: [Description and needs]
## Functional Requirements
### FR-001: [Requirement Name]
**Description**: [Detailed description]
**Priority**: High/Medium/Low
**Acceptance Criteria**:
- [ ] [Specific, measurable criterion]
- [ ] [Another criterion]
## Non-Functional Requirements
### NFR-001: Performance
**Description**: System response time requirements
**Metrics**:
- Page load time < 2 seconds
- API response time < 200ms for 95th percentile
### NFR-002: Security
**Description**: Security and authentication requirements
**Standards**: OWASP Top 10 compliance, SOC2 requirements
## Constraints
- Technical constraints
- Business constraints
- Regulatory requirements
## Assumptions
- [List key assumptions made]
## Out of Scope
- [Explicitly list what is NOT included]
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.
- 10d ago First seen · 228 lines · 49 tokens per session scan A 1e07ae462cfd
spec-analyst is an agent published in the GitHub repository ahmedibrahim085/Claude-Multi-Agent-Research-System-Skill (11 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,383 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-30.
Other agents, from other repositories
bt6-maintainer-steward
Coordinates full-queue maintenance across BT6 research, knowledge, analysis, and support repositories.
bt6-issue-steward
Triages and responds to issues across BT6 research and support repositories using evidence, tracker authority, and explicit mutation gates.
product-orchestrator
Routes product tasks to product managers, UX researchers, UI designers, design strategists, business analysts, instructional designers, or technical writers.
talent-development
Learning programs, career development, performance management. Training, coaching, succession planning.
technical-business-analyst
Requirements gathering, process mapping, technical specifications. Bridge between business needs and engineering.
technical-program-manager
Agile delivery, sprint planning, cross-team coordination. Scrum, Kanban, roadmaps, stakeholder management.