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 anysiteio/agent-skills --skill customer-pain-mininggit clone --depth 1 https://github.com/anysiteio/agent-skillsWrote 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/anysiteio/agent-skills/customer-pain-mining)<a href="https://agentmods.dev/skills/anysiteio/agent-skills/customer-pain-mining"><img src="https://agentmods.dev/badge/skills/anysiteio/agent-skills/customer-pain-mining/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/anysiteio/agent-skills/customer-pain-mining"><img src="https://agentmods.dev/badge/skills/anysiteio/agent-skills/customer-pain-mining.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 286 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00181 | $0.06114 |
| Opus 5 | $0.00090 | $0.03057 |
| Sonnet 5 | $0.00036 | $0.01223 |
| Haiku 4.5 | $0.00018 | $0.00611 |
Grade A, and why
customer-pain-mining 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.
How it starts
The opening of the file, as written. The whole thing — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Pain Mining
Competitors at the early stage aren't a threat — they're a proxy for the customer. Their unhappy users have already done your custdev calls. This skill harvests them.
The goal is verbatim wording, not paraphrase. Founders summarize and lose the gold. Pull exact phrases — they become product copy.
When this skill applies
- A founder asks what users dislike about competitors or the category
- Preparing custdev calls — you want talking points in the customer's own language
- Writing landing-page copy or positioning — you need real pain wording
- Hunting white-space features competitors aren't shipping
- After
competitor-discovery— going deeper on the named players
What you need
- Competitor list — 1 to 5 named competitors (run
competitor-discoveryfirst if there isn't one) - Niche / category — one line for context (e.g. "AI writing for students")
- Use case for the output — affects source weighting:
- Custdev prep → Reddit (long-form verbatim wins)
- Ad copy → Exa for short blog-post pull-quotes
- Product strategy → Exa for structured "Pros / Cons" review pages
Tools
Anysite MCP:
mcp__claude_ai_Anysite__execute(source="reddit", category="search", endpoint="search_posts", params={...})— Reddit posts by query (anonymous, viral, long-form).mcp__claude_ai_Anysite__execute(source="linkedin", category="search", endpoint="search_posts", params={"keywords": "<pain-phrase>", "sort": "relevance", "count": 15})— LinkedIn posts BY professionals describing the pain. Critical: search by the PAIN, not the competitor name (see Step 5).mcp__claude_ai_Anysite__query_cache(cache_key, conditions, ...)— filter cached results (e.g.vote_count > 50).mcp__claude_ai_Anysite__get_page(cache_key, offset)— paginate.mcp__claude_ai_Anysite__execute(source="youtube", category="video", endpoint="video_comments", params={"video": "<id>", "count": 50})— comments under a competitor-review YouTube video; people who watched a 15-min review have committed to evaluating the product. Filterlike_count >= 5. Watch for affiliate astroturf (5+ short identical-tone praises from different accounts).mcp__claude_ai_Anysite__execute(source="twitter", category="search", endpoint="search_posts", params={"query": "<niche+pain>", "min_likes": 5, "count": 20, "language": "English"})— viral short-form pain quotes. Setmin_likes≥ 50 for breakthrough quotes; otherwise filter aggressively for relevance because the query catches handle namesakes (e.g. "Bright" matches users named "Bright").
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 · 319 lines · 181 tokens per session scan A 05fe42f1dc96
customer-pain-mining is a skill published in the GitHub repository anysiteio/agent-skills (19 stars, last pushed 27d ago), licensed MIT. It adds 181 tokens to every session and 6,114 once invoked, about $0.0009 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
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…