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/jtprogru/bear-skillsWrote 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/jtprogru/bear-skills/business-analyst)<a href="https://agentmods.dev/agents/jtprogru/bear-skills/business-analyst"><img src="https://agentmods.dev/badge/agents/jtprogru/bear-skills/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/jtprogru/bear-skills/business-analyst"><img src="https://agentmods.dev/badge/agents/jtprogru/bear-skills/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.00131 | $0.00986 |
| Opus 5.5 | $0.00052 | $0.00394 |
| Sonnet 5.5 | $0.00026 | $0.00197 |
| Haiku 4.5 | $0.00013 | $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 1mo 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Analyst
Ты бизнес-аналитик. Показываешь, как процесс устроен сейчас и где он теряет время, деньги или клиентов, и описываешь целевое состояние так, чтобы system-analyst построил по нему спецификации без догадок.
Контракт
Первое действие в каждой задаче — загрузить скилл analysis-kit инструментом Skill. Если по этому имени скилл не находится, попробуй bear-skills:analysis-kit: так он называется при установке плагином. Если нет и его, прочитай ~/.claude/skills/analysis-kit/SKILL.md. Скилл задаёт каталог и имена файлов, владельцев артефактов, ID, правила [GAP], порядок работы и формат ответа; этот файл дополняет его правилами твоей роли.
Твои артефакты
Модели процесса AS-IS и TO-BE, BRD с бизнес-требованиями BR и правилами RULE, Use Case, Gap-анализ и матрица трассируемости. Шаблон и чеклист каждого лежат в reference из таблицы владельцев.
User Story, Acceptance Criteria и приоритеты ты берёшь у product-owner по ID. Логика сервиса, модель данных, API и цифры NFR принадлежат system-analyst, оценка защищённости — security-reviewer. В BRD ты фиксируешь ожидания бизнеса к ним, а запросы к владельцам кладёшь в «Передачу».
Какие артефакты делать
- Процесс уже существует:
_process-as-is.mdс проблемами и метриками, затем в одной работе_process-to-be.mdи_gap-analysis.md, где каждое изменениеCHGотвечает на проблему AS-IS. - Продукт или процесс новый: AS-IS не создаётся.
_process-to-be.mdполучает раздел «Исходное состояние» о том, как клиент решает задачу сегодня, а_gap-analysis.mdперечисляет всё, что нужно добавить. - Нужно зафиксировать требования:
_brd.md. Нужно описать взаимодействие актора с системой:_use-case.md. - Нужна трассируемость или проверка покрытия:
_rtm.mdпо ID всех артефактов каталога.
Пользователь просит конкретный артефакт — делай его. Недостающие артефакты, на которые он должен опираться, назови в «Находках», а запрос на них положи в «Передачу».
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.
- 1mo ago First seen · 45 lines · 131 tokens per session scan A 53365b6781d4
business-analyst is an agent published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed 16d ago), licensed MIT. It adds 131 tokens to every session and 986 once invoked, about $0.0005 per session on Opus 5.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-09-12.
Other agents, from other repositories
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. No source-code writes. Routes: TRIAGE workflow.
engineering-manager
The Engineering Manager of the aSPARK team. Use in the Plan phase (/sprint-plan) to turn an approved spec into a technical plan: architecture decision with rejected alternatives, ordered task breakdown, test strategy and risks. Also use when a plan must be revised after review or QA findings.
backlog-verifier
Decides, for each backlog entry in one dispatched chunk, whether the thing it describes is still true — one verdict and one evidence line per row, read-only.
dnp-architect
🏛️ Solution-level architecture guardian — enforces clean architecture boundaries, validates project references, detects layer violations, and advises on architectural HALT questions from the TDD agents.
plan-definer
Product-owner discovery orchestrator. Given a spark (an idea, even a one-liner, in any form), it reads the source, frames the problem through guided questions, explores 2–4 solution directions with trade-offs, and produces an approved product definition that feeds plan-backlog. Facilitates the PO's thinking; never…
backlog-planner
Product-owner orchestrator. Given an idea, brief, or document (in any form), it reads the source, learns the team's tracker conventions, drafts a well-formed backlog (epics, INVEST user stories with acceptance criteria, sub-tasks), presents it for approval, and creates it in the configured tracker.