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/pssah4/digital-innovation-agentsnpx agentmods add skills/pssah4/digital-innovation-agents/business-analysisWrote 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/pssah4/digital-innovation-agents/business-analysis)<a href="https://agentmods.dev/skills/pssah4/digital-innovation-agents/business-analysis"><img src="https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/business-analysis/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/pssah4/digital-innovation-agents/business-analysis"><img src="https://agentmods.dev/badge/skills/pssah4/digital-innovation-agents/business-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 22 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 292 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 298 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 130 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00071 | $0.03724 |
| Opus 5 | $0.00036 | $0.01862 |
| Sonnet 5 | $0.00014 | $0.00745 |
| Haiku 4.5 | $0.00007 | $0.00372 |
Grade A, and why
business-analysis 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 12d 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Analyst
The value is the dialog, not the document. You conduct a structured interview to understand the business problem and stakeholder needs; the BA record condenses that dialog into the 40-line template. Write only what was said or evidenced; never invent personas, percentages, or baselines to fill a table.
Conventions linked once. Reader budget, frontmatter spec, backlog
vocabulary, writing style, and section policy all live in
skills/project-conventions/SKILL.md#canonical-specs. Do not restate.
MANDATORY Pre-Phase 0: Branch and item check
Standard ritual, full rules in
skills/project-conventions/references/team-workflow.md: identify the
active item (BACKLOG row first for new items), verify the branch
matches <type>/<item-id-lower>-<slug> (AskUserQuestion on mismatch),
run flow.py create-issue + open-draft-pr when GitHub sync is on,
tag the phase at ritual end (--phase ba), and write
.git/dia-active-skill. Fires once per invocation.
MANDATORY Phase 0: BA target triage
Every BA session targets exactly one item. The triage picks the file and the template:
| Outcome | File | Template | When |
|---|---|---|---|
| Project-BA (singleton) | analysis/BA-{PROJECT}.md |
BA-TEMPLATE | Greenfield or explicit refresh |
| EPIC Item-BA | analysis/BA-EPIC-{nn}-{slug}.md |
BA-TEMPLATE | Mandatory before RE opens an epic |
| FEAT Item-BA | analysis/BA-FEAT-{ee}-{ff}-{slug}.md |
BA-TEMPLATE (reduced) | Mandatory unless parent EPIC-BA covers it |
| IMP Item-BA | analysis/BA-IMP-{ee}-{ff}-{nn}-{slug}.md |
BA-MINI-TEMPLATE | Optional, value or scope unclear |
| FIX Item-BA | analysis/BA-FIX-{ee}-{ff}-{nn}-{slug}.md |
BA-MINI-TEMPLATE | Optional, root cause unclear |
If the target is unclear, ask once:
"Which item is this BA for: Project-BA, a new EPIC, a new FEAT inside an existing epic, or a smaller IMP/FIX?"
Resolve the next free ID, write the BACKLOG row first (status defaults
to Backlog), then continue. The ID is reserved while the BA is in
progress. Details: skills/project-conventions/references/graph-invariants.md.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 379 lines · 71 tokens per session scan A a4a64ea28fe7
business-analysis is a skill published in the GitHub repository pssah4/digital-innovation-agents (39 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 3,724 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-30.
Other skills, from other repositories
ensemble-beads-build
Drive an existing bead hierarchy to completion through the full builder, code-review, and close pipeline (Codex skill for /ensemble:beads-build).
ensemble-beads-plan
Analyze an existing bead hierarchy and produce bv analysis and wheel instructions without executing any implementation (Codex skill for /ensemble:beads-plan).
ensemble-implement-bead
Implement a single beads task by ID through analysis, implementation, and PR creation (Codex skill for /ensemble:implement-bead).
ensemble-refine-beads
Approval-gated Beads graph refinement before execution (Codex skill for /ensemble:refine-beads).
close-the-gaps
Product Analyst session: fetches a ticket, loads project skills, explores affected code, asks gap-analysis questions one at a time, outputs Gherkin-format refined ticket. Use when refining a ticket before dev starts.
complete-beads
Goal-oriented skill that drives every scoped bead to closed or a truthful terminal state. Recovers in-progress work, selects tasks via BV triage/planning, dispatches isolated workers in parallel, integrates serially, and rolls up completed containers. Produces one machine-readable result sentinel.