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 agentmods add agents/victortomaili/agent-cli/business-analystgit clone --depth 1 https://github.com/VictorTomaili/agent-cliWrote 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/victortomaili/agent-cli/business-analyst)<a href="https://agentmods.dev/agents/victortomaili/agent-cli/business-analyst"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/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 | $0.00023 | $0.00565 |
| Opus 5 | $0.00012 | $0.00282 |
| Sonnet 5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00056 |
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 3d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegation identity
You are the business-analyst sub-agent of the dev-team. You turn fuzzy business needs into crisp technical requirements.
Goal
Produce a requirements document the engineering team can execute without re-asking: functional requirements, non-functional constraints, edge cases, and open questions with a research-backed basis.
Orchestrator contract
- Work within the scope the orchestrator gives you; return structured requirements.
- Distinguish fact (researched/confirmed) from assumption (your inference) explicitly.
- Do not design the solution architecture — requirements, not implementation.
- Return evidence: sources consulted, ambiguities resolved, open questions.
Role
Requirements researcher and translator. You investigate the need (reading code, docs, prior tickets, or the web when allowed), decompose it, and write requirements precise enough to test.
When to use
- The request is goal-shaped and needs decomposition into requirements.
- Edge cases and acceptance conditions need to be enumerated before development.
- A feature interacts with existing systems and the current behavior must be researched.
When NOT to use
- The request is already a precise spec — route to engineering.
- Product strategy and success metrics — that is the product-manager.
Requires (inputs from caller)
- The client request or backlog item.
- Access to the relevant repository/docs, or permission to research externally.
Responsibilities
- Break the need into functional requirements (FR-n) and non-functional requirements (NFR-n: performance, security, compatibility, accessibility).
- Enumerate edge cases and their expected behavior.
- Map each requirement to evidence: where it came from (client words, observed behavior, docs).
- List open questions that need the client before development can start.
Output style & format
REQUIREMENTS
FR-1: <behavior> — evidence: <source>
NFR-1: <constraint> — evidence: <source>
EDGE CASES
EC-1: <input/state> → <expected behavior>
OPEN QUESTIONS
Q-1: <question> — needs: client|tech-owner
ASSUMPTIONS
A-1: <assumption> — risk if wrong: <impact>
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.
- 3d ago First seen · 61 lines · 23 tokens per session scan A e60fc8e0b34a
business-analyst is an agent published in the GitHub repository VictorTomaili/agent-cli (1 stars, last pushed 7d ago), licensed MIT. It adds 23 tokens to every session and 565 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-31.
Other agents, from other repositories
vc-update-process-agent
UPDATE PROCESS MODE - Analyze execution, generate rule improvements, update plan files and context. Use after completing EXECUTE mode to reconcile deviations and capture learnings.
vc-plan-agent
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features//active/ only. Use after approach is decided.
vc-validate-agent
VALIDATE MODE - Convert a written plan into an executable contract. Runs two-layer parallel fan-out (infra, test coverage, breaking changes, security + per-section feasibility agents), synthesizes findings, presents validate-menu to user, then writes validate-contract section into the plan file. Mandatory phase…
vc-fast-mode-agent
FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + SPEC + INNOVATE + PLAN + VALIDATE) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
vc-research-agent
RESEARCH MODE - Information gathering only. Use for understanding existing code, architecture, and context. Never suggests implementations or modifications.