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 volodchenkov/claude-sdlc-agents --skill babok-elicitationgit 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/skills/volodchenkov/claude-sdlc-agents/babok-elicitation)<a href="https://agentmods.dev/skills/volodchenkov/claude-sdlc-agents/babok-elicitation"><img src="https://agentmods.dev/badge/skills/volodchenkov/claude-sdlc-agents/babok-elicitation/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/volodchenkov/claude-sdlc-agents/babok-elicitation"><img src="https://agentmods.dev/badge/skills/volodchenkov/claude-sdlc-agents/babok-elicitation.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.00089 | $0.03816 |
| Opus 5 | $0.00044 | $0.01908 |
| Sonnet 5 | $0.00018 | $0.00763 |
| Haiku 4.5 | $0.00009 | $0.00382 |
Grade A, and why
babok-elicitation 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BABOK v3 — Elicitation & Requirements Discipline
This skill encodes a focused subset of BABOK v3 (Business Analysis Body of Knowledge, IIBA, 3rd edition) for the the business-analyst agent. Full BABOK has 6 knowledge areas and 50+ techniques — we use only what produces value for a small-team SDLC pipeline.
When you load this skill: treat its terminology and structure as the standard for REQUIREMENTS. Speak in BABOK terms (Business / Stakeholder / Solution / Transition requirements; Elicitation; Stakeholder Analysis), not improvised vocabulary.
Knowledge areas — what we use, what we skip
| BABOK Knowledge Area | Use? | Why |
|---|---|---|
| Elicitation and Collaboration | ✅ core | the business-analyst's main job — extract truth from initiator |
| Requirements Analysis and Design Definition | ✅ core | Structuring elicited info into REQUIREMENTS |
| Requirements Lifecycle Management | ⚠️ light | Trace via Plane comment history; no formal versioning |
| Business Analysis Planning and Monitoring | ❌ skip | Solo-founder context; no separate planning role |
| Strategy Analysis | ❌ skip | Trim for now; revisit when product-strategy work emerges |
| Solution Evaluation | ❌ skip | Covered downstream by the reviewer (Final Reviewer) |
The 4 requirement types — your mental model
This is the single most useful BABOK insight for the business-analyst. Every requirement you elicit fits exactly one of these:
1. Business Requirements
Higher-level needs of the enterprise. Why are we doing this? What business outcome do we expect?
Examples:
- "Reduce support load from 'where is my order' tickets by 30%"
- "Enable cross-region delivery to expand to Kazakhstan market"
- "Cut average checkout time from 4 minutes to under 2"
Failure mode: project starts without a business requirement → solution looks for a problem.
2. Stakeholder Requirements
Needs of specific actors (users, operators, system administrators, business owners).
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 · 305 lines · 89 tokens per session scan A 4e44738d90d7
babok-elicitation is a skill published in the GitHub repository volodchenkov/claude-sdlc-agents (2 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 3,816 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…