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 skills/pillip/claude-dev-kit/bizanalysisnpx skills add pillip/claude-dev-kit --skill bizanalysisgit clone --depth 1 https://github.com/pillip/claude-dev-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/skills/pillip/claude-dev-kit/bizanalysis)<a href="https://agentmods.dev/skills/pillip/claude-dev-kit/bizanalysis"><img src="https://agentmods.dev/badge/skills/pillip/claude-dev-kit/bizanalysis.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.00020 | $0.01969 |
| Opus 5 | $0.00010 | $0.00984 |
| Sonnet 5 | $0.00004 | $0.00394 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
bizanalysis 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kit Preamble — bizanalysis
Kit Script Root
Kit root: ${CLAUDE_PLUGIN_ROOT}
- Absolute path above → plugin install (substituted at load time; no project
scripts/dir): prefix every kit script command with it, e.g.bash <kit-root>/scripts/checkpoint.sh …. Absolute paths also work from worktrees. - Literal
${…}placeholder above → standalone layout: run commands as written.
Project Context Detection
Run these checks silently at the start. Use results to adapt behavior:
[ -f issues.md ]— if true, this project uses the sprint system. Respect issue numbering and STATUS.md.[ -f docs/sprint_state.md ]— if true and Status showsrunning, a sprint is active. Be aware of parallel work in worktrees.[ -f docs/prd_digest.md ]— if true, read it for quick project context before starting.
Kit Rules
- Verify
gh auth statusbefore any GitHub operation. Steps:
- Determine the output path ($ARGUMENTS or
docs/business_analysis.md). - Check if the file already exists at that path.
- Check if
docs/brainstorm_notes.mdexists. If it does, read it and use as context — problem space, target users, chosen direction. - Probe runtime (per SPEC-018 platform-first delegation):
python3 scripts/has_skill.py deep-research. Branch:- Exit 0 OR 2 → primary path (steps 5–9 use
/deep-researchper dimension). - Exit 1 → degraded path (steps 5–9 use
capture_source.py+validate_research_claim.pyper source).
- Exit 0 OR 2 → primary path (steps 5–9 use
If the file does NOT exist (New Analysis):
5a) If brainstorm notes exist, summarize the idea from them. Otherwise, ask the user to describe their idea.
Primary path (runtime probe = 0 or 2):
6a-P) Market Analysis: invoke /deep-research with a refined question about market size, trends, and TAM/SAM/SOM for the specific segment. Emit telemetry event research_delegated_to_deep_research.
7a-P) Competitive Landscape: invoke /deep-research with a refined question about direct competitors, alternatives, and positioning differences. Emit research_delegated_to_deep_research.
8a-P) Business Model + Risks: invoke /deep-research with a refined question about prevailing revenue models in the segment and the key market / regulatory / competitive risks. Emit research_delegated_to_deep_research.
9a-P) Synthesize: pass the per-dimension /deep-research reports through python3 scripts/synthesize_from_deep_research.py --mode bizanalysis. The synthesizer maps cited claims into the kit's 5-section template, preserves [single-source] / [contested] flags verbatim from upstream, and renders empty sections as the literal line Data: not available — re-run /deep-research with a sharper question or accept "no data".
10a-P) Audit: invoke Task with subagent_type: synthesizer-auditor, inputs = (rendered draft, all /deep-research reports). Block save on claim_dropped / claim_distorted / evidence_distorted / scope_change findings until resolved.
What ships with it
1 file 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.
- 3d ago First seen · 94 lines · 20 tokens per session scan A 79e8be7947bd
bizanalysis is a skill published in the GitHub repository pillip/claude-dev-kit (11 stars, last pushed 17d ago), licensed MIT. It adds 20 tokens to every session and 1,969 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 skills, from other repositories
knowledge-base
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…
peer-review
Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating…
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约,产出 UI-DESIGN.md。四端通用。.
taiyi-evolve
TaiyiForge 辅助 — 实现后架构与文档同步(architecture-sync)。OpenCode / Claude / Codex / Cursor 通用。.