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/zircote-plugins/sigint/market-sizingnpx skills add zircote-plugins/sigint --skill market-sizinggit clone --depth 1 https://github.com/zircote-plugins/sigintWrote 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/zircote-plugins/sigint/market-sizing)<a href="https://agentmods.dev/skills/zircote-plugins/sigint/market-sizing"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sigint/market-sizing.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.00066 | $0.02833 |
| Opus 5 | $0.00033 | $0.01417 |
| Sonnet 5 | $0.00013 | $0.00567 |
| Haiku 4.5 | $0.00007 | $0.00283 |
Grade A, and why
market-sizing 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 5d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Sizing (TAM/SAM/SOM)
Overview
Market sizing quantifies the revenue opportunity in a market. The TAM/SAM/SOM framework provides progressively refined estimates from total market to realistically achievable share.
Required Frameworks
| Framework | Output Section | Required | Condition |
|---|---|---|---|
| Methodology Selection | methodology rationale | yes | — |
| TAM/SAM/SOM Hierarchy | Market Sizing Summary | yes | — |
| Scenario Modeling | Scenarios | yes | — |
| Growth Projections | CAGR/growth | yes | — |
Trend Indicators: Load and apply the trend indicator definitions from protocols/TREND-INDICATORS.md.
Key Definitions
TAM (Total Addressable Market)
- Total global market demand for a product/service
- Assumes 100% market share (theoretical maximum)
- Useful for understanding ceiling and investor conversations
SAM (Serviceable Addressable Market)
- Portion of TAM targetable with current business model
- Considers geographic, demographic, or segment constraints
- More realistic than TAM
SOM (Serviceable Obtainable Market)
- Realistic market share achievable in near term (1-3 years)
- Considers competition, resources, and go-to-market capability
- Most relevant for planning
Methodology Selection Guide
| User Signal | Recommended Methodology |
|---|---|
| "TAM SAM SOM", "market opportunity", no pricing data | Top-Down |
| Provides pricing, unit counts, or customer data | Bottom-Up |
| Mentions "value", "pain point cost", "willingness to pay" | Value Theory |
| "bottom-up" explicitly requested | Bottom-Up |
| "growth trends", "CAGR", trend questions | Top-Down + Trend Analysis |
| "bear/base/bull", "scenarios" | Any methodology + Scenario Modeling |
| Vague with no segment specified | Top-Down (state assumptions) |
| Market known to be declining | Top-Down + DEC trend handling |
Calculation Methodologies
Top-Down Approach
Start with large market data, narrow down:
What ships with it
4 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.
- 5d ago First seen · 287 lines · 66 tokens per session scan A d7bd28228ab7
market-sizing is a skill published in the GitHub repository zircote-plugins/sigint (20 stars, last pushed 19d ago), licensed MIT. It adds 66 tokens to every session and 2,833 once invoked, about $0.0003 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
gr-competitor
竞品深度扫描。批量抓取对手落地页（title/h1/intro/pricing）、定价页、博客 top 10、 变更历史（Wayback）。底层调 actionbook（并发 30 tab + 省 90% token）。 当用户说"分析对手"、"看看竞品在做啥"、"找对标"、"扫一下 top 10"时调用。.
radar-merge-briefing
Merges all competitor dossiers and the change set into one briefing. Writes three local artifacts: the briefing markdown, a combined raw dossier JSON, and a dashboard data JSON. Use after radar-diff-changes and before radar-publish-notion and radar-render-dashboard. Every claim in the briefing carries a source URL.
radar-publish-council
Publishes the Strategic War Room addendum from /radar-council to all three surfaces. Appends the addendum to the local briefing markdown, fills the warroom section of the dashboard data and re-renders the dashboard, and appends the addendum to the Notion briefing page while checking its War Room box. Use after the…
radar-onboard
Run this FIRST, before any other radar skill. Sets up Competitive Intelligence Radar by ASKING whether BrightData and Notion are connected, live-testing one real call to each, detecting which MCP prefix is actually live, and writing radar.config.json with the user's business context. Use when the user runs…
radar-diff-changes
Diffs this run's competitor dossiers against the previous run to find what materially changed (SERP moves, price changes, new news, sentiment shifts, new or dropped competitors). Produces a ranked change set the briefing and dashboard use. Use after all competitor-scout subagents have written their dossiers and before…
radar-provision-notion
Creates the two Notion databases (Competitors and Briefings) the radar publishes to, but ONLY after SHOWING the proposed schema and getting the user's explicit approval. Use during /radar-setup after onboarding, or when radar-publish-notion reports the databases are missing. Idempotent: if the databases already exist…