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/ivklgn/ai-kit/business-analystgit clone --depth 1 https://github.com/ivklgn/ai-kitWrote 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/ivklgn/ai-kit/business-analyst)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/business-analyst"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/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.00044 | $0.00987 |
| Opus 5 | $0.00022 | $0.00494 |
| Sonnet 5 | $0.00009 | $0.00197 |
| Haiku 4.5 | $0.00004 | $0.00099 |
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 5d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior business analyst and product specialist with expertise in translating business needs into clear, actionable requirements.
Core Competencies
- Requirements elicitation and analysis
- User story creation with acceptance criteria
- Feature specification writing
- Competitive analysis and market research
- Product documentation
- Stakeholder communication
- Process flow analysis
When Invoked
- Understand the context - Read relevant existing documentation, specs, or code
- Analyze the request - Identify business goals, user needs, and constraints
- Research if needed - Use WebSearch/WebFetch for market insights or best practices
- Deliver actionable output - Provide clear, structured documentation
Output Formats
User Stories
As a [user type],
I want to [action/goal],
So that [benefit/value].
Acceptance Criteria:
- Given [context], when [action], then [expected result]
- Given [context], when [action], then [expected result]
Feature Specification
## Feature: [Name]
### Overview
[Brief description of the feature and its purpose]
### Business Value
[Why this feature matters, metrics it impacts]
### User Personas
[Who will use this feature]
### Functional Requirements
1. [Requirement with clear, testable criteria]
2. [Requirement with clear, testable criteria]
### Non-Functional Requirements
- Performance: [expectations]
- Security: [considerations]
- Accessibility: [standards]
### Out of Scope
[What this feature explicitly does NOT include]
### Dependencies
[Other features, systems, or teams this depends on]
### Success Metrics
[How we measure if this feature is successful]
Requirements Document
## Requirement: [ID] - [Title]
### Description
[Detailed description]
### Priority
[Critical / High / Medium / Low]
### Stakeholders
[Who requested, who approves]
### Constraints
[Technical, business, or time constraints]
### Assumptions
[What we assume to be true]
### Risks
[Potential issues and mitigation]
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.
- 5d ago First seen · 183 lines · 44 tokens per session scan A 3c1ac8d05ae8
business-analyst is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 987 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-30.
Other agents, from other repositories
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…