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 skills add shinpr/nautilus --skill business-contextgit clone --depth 1 https://github.com/shinpr/nautilusWrote 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/nautilus/business-context)<a href="https://agentmods.dev/skills/shinpr/nautilus/business-context"><img src="https://agentmods.dev/badge/skills/shinpr/nautilus/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.00296 |
| Opus 5 | $0.00023 | $0.00148 |
| Sonnet 5 | $0.00009 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00030 |
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 8d 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.
What it actually says
Business Context Analysis
Purpose
Select the business evidence and framework needed to change a current Opportunity, Value, or Viability decision.
When to Use Each Framework
| Framework | Use When | Key Output |
|---|---|---|
| Business Model Canvas | Understanding or designing the business model | 9-component business model 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 |
Read only the selected reference. Extract evidence rather than reproducing the framework:
references/business-model-canvas.mdfor business-model fit and Viability dependenciesreferences/value-proposition-canvas.mdfor jobs, pains, gains, and Problem-Solution Fitreferences/market-analysis.mdfor market size, segmentation, competition, trends, or gaps
Key Principles
- Cite sources for market claims and label estimates or assumptions.
- Revalidate source age only when changed conditions can affect the current decision.
- Cross-check a claim when the decision depends on a contested estimate.
- Stop when additional business context cannot change the Opportunity or risk decision.
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.
- 8d ago First seen · 32 lines · 45 tokens per session scan A de617865a557
business-context is a skill published in the GitHub repository shinpr/nautilus (4 stars, last pushed 7d ago), licensed MIT. It adds 45 tokens to every session and 296 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
productspec
Use when implementing, reviewing, planning, or changing work governed by a Product Spec. Treat .product-spec.md files as the product contract for the work.
productspec-authoring
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Use when authoring a new Product Spec, converting an existing PRD or feature doc into one, validating spec files locally or in CI, or recording how a spec's intent changed over…
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.
recipe-define
Orchestrate PRD creation from validated hypotheses — standard PRD output with 4 Risks confidence and hypothesis traceability.
recipe-validate
Orchestrate hypothesis validation through type-appropriate methods — prototypes, code analysis, market research, and expert review.
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.