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 varunk130/ai-gtm-skill-library --skill market-analyzergit clone --depth 1 https://github.com/varunk130/ai-gtm-skill-libraryWrote 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/varunk130/ai-gtm-skill-library/market-analyzer)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/market-analyzer"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/market-analyzer/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/varunk130/ai-gtm-skill-library/market-analyzer"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/market-analyzer.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.00066 | $0.01057 |
| Opus 5 | $0.00033 | $0.00528 |
| Sonnet 5 | $0.00013 | $0.00211 |
| Haiku 4.5 | $0.00007 | $0.00106 |
Grade A, and why
market-analyzer 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Analyzer (SCOPE Framework)
Full-spectrum market analysis producing investment-grade market maps with sizing, growth drivers, risk factors, and segment-level deep dives. Goes beyond basic TAM/SAM/SOM.
When to Use
- New market entry decisions
- Board/investor market briefings
- Product strategy validation
- Fundraising market slides
- Annual strategic planning
What You'll Need
Critical inputs (ask if not provided):
- Market or product category to analyze
- Geographic scope (global, US, EMEA, etc.)
- Time horizon (current year + forecast period)
Nice-to-have:
- Whitespace Finder output (opportunities to size)
- Signal Radar output (trends affecting the market)
- Existing market data or analyst reports
Process
Step 1: Market Definition
Before sizing, rigorously define the market boundaries:
- Category definition: What products/services are included? What is excluded?
- Buyer definition: Who purchases? (roles, company types, segments)
- Use case definition: What problems does this market solve?
- Adjacent markets: What related markets overlap or compete for budget?
Step 2: SCOPE Analysis
Analyze the market across 5 structural dimensions:
| Dimension | What It Covers | Key Questions |
|---|---|---|
| Size & Growth | TAM/SAM/SOM + growth trajectory | How big? How fast growing? Top-down AND bottom-up? |
| Competitive Density | Number and strength of competitors | How crowded? Any dominant players? Fragmented or consolidated? |
| Opportunity Windows | Timing-sensitive opportunities | What market shifts create openings? What is the window duration? |
| Power Dynamics | Who holds power in the value chain | Buyer power? Supplier power? Platform dependencies? Regulatory influence? |
| Economic Drivers | What drives market growth or contraction | Macro trends? Technology adoption curves? Budget cycle patterns? |
Step 3: Multi-Method Sizing
Use THREE methods and triangulate:
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 · 101 lines · 66 tokens per session scan A 5afb1c3ed9f8
market-analyzer is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (6 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 1,057 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-31.
Other skills, from other repositories
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…