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 cdeistopened/skill-stack --skill niche-scoutgit clone --depth 1 https://github.com/cdeistopened/skill-stackWrote 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/cdeistopened/skill-stack/niche-scout)<a href="https://agentmods.dev/skills/cdeistopened/skill-stack/niche-scout"><img src="https://agentmods.dev/badge/skills/cdeistopened/skill-stack/niche-scout/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/cdeistopened/skill-stack/niche-scout"><img src="https://agentmods.dev/badge/skills/cdeistopened/skill-stack/niche-scout.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.00038 | $0.01348 |
| Opus 5.5 | $0.00015 | $0.00539 |
| Sonnet 5.5 | $0.00008 | $0.00270 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
niche-scout 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 1mo 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Niche Scout
Evaluate whether a keyword/topic is a profitable KDP publishing niche. Based on the 3-step validation framework from Sean Dollwet, Dale Roberts, and Dave Chesson (175 episodes distilled in Kings of Kindle).
Usage
/niche-scout beekeeping for beginners
/niche-scout "anxiety management"
/niche-scout claude code AI coding assistant
Workflow
Step 1: Amazon Keyword Volume (DataForSEO)
Run the keyword volume script to get Amazon search volume and related keywords:
python3 ~/.claude/skills/niche-scout/scripts/keyword-volume.py "$ARGUMENTS"
This returns:
- Amazon search volume for the seed keyword + 9 variations
- Related keywords with volume (up to 20)
- Use these to assess demand and identify series potential (10-keyword strategy)
Demand threshold: Seed keyword should have 200+ monthly Amazon searches. Related keywords reveal series opportunities.
Step 2: BSR Analysis (Apify Amazon Scraper)
Run the BSR scraper to get Best Seller Rank for top books:
python3 ~/.claude/skills/niche-scout/scripts/bsr-scraper.py "$ARGUMENTS"
This runs two Apify calls:
- Search results — gets titles, prices, ratings, ASINs for top 20 books
- Product details — gets BSR, publisher, categories for top 10
Wait for both to complete (typically 30-90 seconds each).
Step 3: Score the Niche
Apply Sean Dollwet's BSR benchmarks to the scraped data:
| Metric | Target | Scoring |
|---|---|---|
| Books under 5,000 BSR | No more than 5 of top 20 | >5 = too competitive |
| Books under 30,000 BSR | Most or all of top 20 | Sweet spot for new publishers |
| Books under 100,000 BSR | At least 7 of 10 | Minimum viable demand |
| Self-published on page 1 | At least 2-3 | Proves indie can compete |
| Search results count | Under 3,000 | Lower = easier to rank |
Self-published detection signals:
- Publisher = "Independently published" or "Independently Published"
- Price $2.99-$4.99 range
- Keyword-heavy title (exact match of search term)
- Stock/template cover design
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.
- 1mo ago First seen · 136 lines · 38 tokens per session scan A db1a3ca7db3e
niche-scout is a skill published in the GitHub repository cdeistopened/skill-stack (30 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 1,348 once invoked, about $0.0002 per session on Opus 5.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
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.