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 skills add gmdaos/business-requirements-analyst --skill business-requirements-analystgit clone --depth 1 https://github.com/gmdaos/business-requirements-analystWrote 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/skills/gmdaos/business-requirements-analyst/business-requirements-analyst)<a href="https://agentmods.dev/skills/gmdaos/business-requirements-analyst/business-requirements-analyst"><img src="https://agentmods.dev/badge/skills/gmdaos/business-requirements-analyst/business-requirements-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/skills/gmdaos/business-requirements-analyst/business-requirements-analyst"><img src="https://agentmods.dev/badge/skills/gmdaos/business-requirements-analyst/business-requirements-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.00079 | $0.03273 |
| Opus 5.5 | $0.00032 | $0.01309 |
| Sonnet 5.5 | $0.00016 | $0.00655 |
| Haiku 4.5 | $0.00008 | $0.00327 |
Grade A, and why
business-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.
How it starts
The opening of the file, as written. The whole thing — 551 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Gathering
This Skill provides a professional and complete methodology for conducting requirements gathering that covers all business layers, not just "the app" or "the system."
Fundamental Principle
Requirements gathering is NOT just a list of functionalities.
Good requirements gathering covers all business layers:
- 🧠 Idea and objective
- 👥 Users
- 💼 Operation
- 💰 Money
- ⚙️ Technology
- ⚠️ Risks
- 📈 Growth
- 🔗 Traceability (from Business to Code)
- ⚖️ Quality Gates (Validation standards)
Available Methodologies
1. Design Thinking (for new ideas)
Ideal when:
- The idea is still being validated
- Not everything is clear
- You want to truly understand the user
Phases:
- Empathize - Understand users
- Define - Identify key problems
- Ideate - Generate solutions
- Prototype - Create early versions
- Test - Validate with real users
Note: Used to discover what to build, not to document everything.
2. Business Analysis (BABOK)
The most complete and professional.
Covers:
- Business requirements
- Functional requirements
- Non-functional requirements
- Business rules
- Stakeholders
- Processes
Note: This is what's used to create formal documents.
3. Lean / Startup Canvas (quick vision)
Useful for:
- Organizing the idea
- Seeing if the business makes sense
⚠️ Important: DOES NOT replace complete requirements gathering.
Recommended Approach
Combine 3 key elements:
- Business vision
- Processes
- System / product
- Traceability & Validation (Ensure everything is connected and meets quality standards)
And document everything in a single master artifact or a structured layer system.
Structure of the Complete Requirements Document
📌 1. Business Vision
Include:
- Problem solved - What pain or need does it address?
- Value proposition - Why is it better than alternatives?
- Business objective - Clear and measurable goals
- Main KPIs - Success metrics
- Scope - What IS and what is NOT included
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 551 lines · 79 tokens per session scan A d357a20595b0
business-requirements-analyst is a skill published in the GitHub repository gmdaos/business-requirements-analyst (7 stars, last pushed 8mo ago), licensed MIT. It adds 79 tokens to every session and 3,273 once invoked, about $0.0003 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 skills, from other repositories
contract-and-proposal-writer
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting…
chief-data-officer-advisor
Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data…
vpe-advisor
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and…
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…
general-counsel-advisor
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…