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 uthumany/uthy-legacy-os --skill market-sizinggit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/market-sizing)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/market-sizing"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/market-sizing/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/uthumany/uthy-legacy-os/market-sizing"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/market-sizing.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.01032 |
| Opus 5 | $0.00017 | $0.00516 |
| Sonnet 5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
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 11d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Sizing
Overview
Market sizing answers one question: how big is this opportunity? It's a critical input for prioritization, fundraising, and strategic planning. This skill guides you through TAM (Total Addressable Market), SAM (Serviceable Addressable Market), and SOM (Serviceable Obtainable Market) estimation using both top-down (macro data) and bottom-up (unit economics) approaches.
When to Use
- Evaluating whether to enter a new market
- Building a business case for a new product
- Preparing for investor pitches or board reviews
- Comparing multiple opportunity areas
- Don't use for: feature-level decisions (too noisy), already-proven markets (sizing is implied)
Instructions
1. Define Your Market
Top-down approach:
- Start with a broad market number (industry reports, analyst data)
- Apply filters to narrow to your addressable segment
- Adjust for geography, business size, or other constraints
Bottom-up approach (preferred for accuracy):
- Define your target customer unit (user, seat, account, transaction)
- Estimate number of target customers
- Multiply by expected price per unit
- Adjust for adoption rate over time
2. Calculate TAM
TAM = total revenue opportunity if you had 100% market share.
- Top-down: Find industry revenue → multiply by your segment's share
- Bottom-up: (Total potential customers × Price per customer/year)
- Be explicit about your assumptions — document each one
3. Calculate SAM
SAM = the portion of TAM you can reach with your current or planned offering.
- Apply filters: geography, segment, use case compatibility
- Example: If TAM is $10B but you only serve mid-market US companies, SAM might be $500M
4. Calculate SOM
SOM = the portion of SAM you can realistically capture in the near term (3-5 years).
- Based on capacity: sales team size, distribution channels, marketing budget
- Based on competitive position: realistic market share given your differentiation
- SOM is usually 1-10% of SAM for new entrants
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.
- 11d ago First seen · 103 lines · 35 tokens per session scan A ad7bfc6d4949
market-sizing is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 1,032 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…