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/shinpr/claude-code-discover/business-contextnpx skills add shinpr/claude-code-discover --skill business-contextgit clone --depth 1 https://github.com/shinpr/claude-code-discoverWrote 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/shinpr/claude-code-discover/business-context)<a href="https://agentmods.dev/skills/shinpr/claude-code-discover/business-context"><img src="https://agentmods.dev/badge/skills/shinpr/claude-code-discover/business-context.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.1 | $0.00045 | $0.00615 |
| Opus 5 | $0.00023 | $0.00308 |
| Sonnet 5 | $0.00009 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
business-context 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 6d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Context Analysis
Purpose
Provide structured frameworks for understanding the business environment surrounding product decisions. These frameworks help assess Viability risk and identify Opportunities through market gaps.
When to Use Each Framework
| Framework | Use When | Key Output |
|---|---|---|
| Business Model Canvas | A viability decision depends on cross-component business-model effects | Decision-relevant component map |
| Value Proposition Canvas | Designing value propositions that match user needs | Customer Profile + Value Map fit |
| Market Analysis | Understanding market size, competition, and trends | Market sizing, competitive positioning |
Business Model Canvas (BMC)
Offers nine business-model components: Customer Segments, Value Propositions, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partnerships, and Cost Structure. Inspect the components and interactions that can change the current viability decision; use a full canvas only when the whole model is the named output.
Use during Opportunity Discovery to understand business context and identify where Solutions must fit within the business model.
See references/business-model-canvas.md for the full framework and quality checklist.
Value Proposition Canvas (VPC)
Designs value propositions by mapping Customer Profile (Jobs, Pains, Gains) to Value Map (Products & Services, Pain Relievers, Gain Creators). The goal is Problem-Solution Fit.
Connection to OST
- Customer Jobs surface Opportunities (unmet jobs = opportunities)
- Pains generate Hypotheses about friction causes
- Pain Relievers and Gain Creators supply assumptions that may affect Value, Usability, Feasibility, or Viability depending on the claim being tested
See references/value-proposition-canvas.md for the full framework and fit assessment checklist.
Market Analysis
Structures market research across: Market Size (TAM/SAM/SOM), Segmentation, Competitive Analysis, and Market Trends.
What ships with it
3 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.
- 6d ago First seen · 60 lines · 45 tokens per session scan A 8ad3c5d8a7e8
business-context is a skill published in the GitHub repository shinpr/claude-code-discover (10 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 615 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-31.
Other skills, from other repositories
product-principles
Defines 4 Risks confidence thresholds, OST hierarchy levels, Knowledge Pyramid tiers, and state design requirements. Use when evaluating user stories, setting confidence scores, referencing OST levels, scoping MVP, or determining validation sufficiency.
hypothesis-discipline
Manages hypothesis lifecycle, enforces validation criteria, time budgets, and confidence scoring rules. Use when creating hypotheses, updating confidence scores, setting validation criteria, handling timeouts, or recording validation results.
blueprint-standards
Defines structural design artifact formats — information architecture, user flows, content model, brand direction, Visual Tokens, and AI interaction model. Use when creating or reviewing design artifacts that precede prototype generation.
recipe-validate
Validates a hypothesis with a risk-appropriate method and records decision-relevant evidence. Use when testing Value, Usability, Feasibility, or Viability assumptions.
recipe-define
Creates a delivery-ready PRD from validated hypotheses with material 4 Risks evidence and necessary traceability. Use when turning validation results into requirements or user stories.
recipe-discover
Frames product Opportunities and creates decision-relevant hypotheses from available evidence. Use when exploring a problem, market opportunity, or user need.