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 kenshikobayashi/everything-claude-code-for-business --skill market-scangit clone --depth 1 https://github.com/kenshikobayashi/everything-claude-code-for-businessWrote 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/kenshikobayashi/everything-claude-code-for-business/market-scan)<a href="https://agentmods.dev/skills/kenshikobayashi/everything-claude-code-for-business/market-scan"><img src="https://agentmods.dev/badge/skills/kenshikobayashi/everything-claude-code-for-business/market-scan/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/kenshikobayashi/everything-claude-code-for-business/market-scan"><img src="https://agentmods.dev/badge/skills/kenshikobayashi/everything-claude-code-for-business/market-scan.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.00010 | $0.00381 |
| Opus 5 | $0.00005 | $0.00191 |
| Sonnet 5 | $0.00002 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
market-scan 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 12d 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
You are executing the /market-scan command. Conduct a market intelligence scan.
Input
$ARGUMENTS — Industry, market segment, or specific topic, optionally with:
--depth [quick|standard|deep]: Analysis depth (default: standard)
Steps
- Research using web search and available data:
- Market size and growth (TAM/SAM/SOM where applicable)
- Key players and market shares
- Recent trends and developments
- Technology shifts
- Regulatory changes
- Analyze using the business-analyst agent's frameworks
- Synthesize into a concise intelligence brief
Output Format
## Market Scan: [Topic]
**Date**: YYYY-MM-DD | **Depth**: [quick|standard|deep]
### Key Findings
1. [Most important insight]
2. [Second]
3. [Third]
### Market Overview
- **Size**: [with methodology]
- **Growth**: [rate and direction]
- **Key Drivers**: [what's pushing growth/decline]
### Competitive Landscape
| Player | Position | Recent Moves | Threat Level |
|--------|----------|-------------|-------------|
### Trends to Watch
1. [Trend] — Impact: [High/Med/Low], Timeline: [Near/Mid/Long-term]
### Implications
- **Opportunity**: [what we can act on]
- **Risk**: [what we need to watch]
- **Recommended action**: [specific next step]
### Sources
[Cited with dates]
Constraints
- Always cite sources with dates
- Clearly distinguish facts from inferences
- Use confidence levels for estimates
- Acknowledge information gaps
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.
- 12d ago First seen · 60 lines · 10 tokens per session scan A fd2dfea8bc9a
market-scan is a skill published in the GitHub repository kenshikobayashi/everything-claude-code-for-business (2 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 381 once invoked, about $0.0001 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…