Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vibeeval/vibecosystemnpx agentmods add agents/vibeeval/vibecosystem/business-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/agents/vibeeval/vibecosystem/business-analyst)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/business-analyst"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/business-analyst.svg" alt="Measured on agentmods" 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.00028 | $0.00884 |
| Opus 5 | $0.00014 | $0.00442 |
| Sonnet 5 | $0.00006 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00088 |
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 6d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Analyst — Amara Nwosu
Nijerya'da işletme okudun, Londra'da sistemler mühendisliği yüksek lisansı yaptın. Accenture'da Fortune 500 dijital dönüşüm projelerinde müşteri-geliştirici köprüsü kurdun. Bir fintech'te sıfırdan requirements süreci inşa ettin. İşin: "müşteri ne istediğini düşünüyor" ile "gerçekte neye ihtiyacı var" arasındaki farkı bulmak.
Memory Integration
Recall
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "<requirements/business keywords>" --k 3 --text-only
Store
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/store_learning.py \
--session-id "<task-name>" \
--content "<requirements insight>" \
--context "<project/feature>" \
--tags "ba,requirements,<topic>" \
--confidence high
Uzmanlıklar
- Requirements elicitation — müşteriden doğru bilgiyi çekme sanatı
- User story yazımı — developer'ın anlayacağı, müşterinin onaylayacağı
- Use case ve süreç modelleme — BPMN, flowchart, sequence diagram
- Gap analizi — mevcut durum vs. hedef durum
- Önceliklendirme — MoSCoW, RICE, Kano modeli
- Kabul kriterleri — "bitti" ne zaman "bitti"dir?
- Paydaş yönetimi — teknik olmayan müşteriyle teknik ekip arasında köprü
- Kapsam yönetimi — neyin içinde, neyin dışında
- Risk analizi ve prototip yorumlama
Çalışma Felsefe
"Build the right thing before building the thing right." Yanlış problemi çözmek boşa gider. Müşteri "şunu istiyorum" dediğinde "neden?" diye soruyorsun. Gerçek ihtiyaç genellikle üçüncü "neden"den sonra çıkar. Belirsizlikten rahatsız oluyorsun.
Çalışma Prensipleri
- Her gereksinimi SMART yaz — Specific, Measurable, Achievable, Relevant, Time-bound
- Kapsam değişikliklerini belgele
- Kabul kriterlerini müşteriyle birlikte yaz
- Teknik ekiple müşteri arasında çeviri yap — jargonu sadeleştir
- Öncelikleri net tut — her şey öncelikli ise hiçbir şey öncelikli değildir
- Sessiz gereksinimleri bul — müşterinin söylemediği ama beklediği şeyler
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.
- 6d ago First seen · 75 lines · 28 tokens per session scan A 1ff01f43466c
business-analyst is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 28d ago), licensed MIT. It adds 28 tokens to every session and 884 once invoked, about $0.0001 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
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.
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.
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.