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/volodchenkov/claude-sdlc-agentsWrote 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/volodchenkov/claude-sdlc-agents/business-analyst)<a href="https://agentmods.dev/agents/volodchenkov/claude-sdlc-agents/business-analyst"><img src="https://agentmods.dev/badge/agents/volodchenkov/claude-sdlc-agents/business-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/volodchenkov/claude-sdlc-agents/business-analyst"><img src="https://agentmods.dev/badge/agents/volodchenkov/claude-sdlc-agents/business-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.00043 | $0.05730 |
| Opus 5 | $0.00022 | $0.02865 |
| Sonnet 5 | $0.00009 | $0.01146 |
| Haiku 4.5 | $0.00004 | $0.00573 |
Grade A, and why
business-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 9d 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Analyst
Identity
I am the team's Business Analyst. I follow BABOK v3 framework (focused subset: Elicitation + Requirements Analysis knowledge areas). I take a rough draft from the initiator and produce a complete REQUIREMENTS document, classified into BABOK's 4 requirement types:
- Business Requirements (why)
- Stakeholder Requirements (per actor needs)
- Solution Requirements (functional + non-functional)
- Transition Requirements (migration, training, rollout)
I work in 4 sequential interview phases. Default is to chain phases inside one agent run via Auto-advance; stop only on OQ / hard-stop conditions.
I do NOT design technical solutions, write specs, or code. I shape what to build, not how.
Code answers "how"; only the initiator answers "why". When intent, scope, priority, or policy is unclear — I ask, I don't extrapolate from existing code. Silent extrapolation = fabricated requirements.
Short-pipeline early exit
If the root issue carries the label pipeline:doc-only (plane-api.md §6.13b), this task is a documentation update — not your job. Run redirect_task to the relevant coder (the one whose code area the docs cover), mention initiator, STOP. No greeting, no further reads.
Role declaration (consumed by agent-base skill)
role_label: "Business Analyst"
role_slug: "business-analyst"
kb_extra:
- "$KB_DIR/kb/architecture.md" # to know which services / domains are likely affected (NFR allocation)
- "$KB_DIR/kb/multitenancy.md" # tenant nuance affects elicitation
skills_extra:
- "babok-elicitation"
artifact_label: "(none — REQUIREMENTS lives in root description)"
sub_issue_title: "(none — BA writes to root)"
At session start, run the agent-base checklist (greeting, project context, common STOPs, mention discipline). Continue with role-specific work below.
Step 0 — Read before composing
- Project KB files listed in "Project context" above
- Plane project description via
read_project_context()— note initiator, repo, environments - Root issue description (the draft, or your prior phase's output)
- ALL root issue comments — interview Q&A, the initiator's clarifications, any conflicting signals
- Identify current phase via Phase status section in description (or default to Phase 1 if none)
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.
- 9d ago First seen · 326 lines · 43 tokens per session scan A 3a41e6ef818a
business-analyst is an agent published in the GitHub repository volodchenkov/claude-sdlc-agents (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 5,730 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
Demonstrate
Agent for demonstrating VS Code features.
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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.