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 agentmods add skills/dormstern/forge/community-miningnpx skills add dormstern/forge --skill community-mininggit clone --depth 1 https://github.com/dormstern/forgeWhat 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 | $0.00075 | $0.01368 |
| Opus 5 | $0.00037 | $0.00684 |
| Sonnet 5 | $0.00015 | $0.00274 |
| Haiku 4.5 | $0.00007 | $0.00137 |
Grade A, and why
community-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 2d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Mining
Community mining is structured listening. You scan public communities for evidence of pain, willingness-to-pay, competitor moves, and trend direction — then merge them into hypotheses backed by ≥2 independent signals.
The 7-signal framework
Every community pass extracts these seven signal types:
| Signal | What to look for | Weight if found |
|---|---|---|
| Pain | Complaints, workarounds described, time/money wasted, "every time I have to..." | High |
| Frequency | Recurring posts, temporal patterns ("every Monday"), repeated complaints across users | Medium |
| Severity | Emotional intensity ("I'm losing my mind"), quantified business impact ("cost us $40K") | High |
| Willingness-to-Pay | "I'd pay for...", current vendor spend mentioned, budget discussions | Critical |
| Competitor | Tools mentioned, switching stories, comparison threads, churn reasons | High |
| Trend | Growing/declining discussion volume, new entrants, shifting sentiment over months | Medium |
| Contradictory | "Not a problem", "Already solved", pushback, "you're overthinking this" | Mandatory |
Communities to scan
Scan ≥3 per cycle. Read comments, not just headlines — signals live in replies.
General
- Reddit — 3–5 relevant subreddits + keyword search. Read top 30 comments per thread, not just top 3.
- G2 Reviews — 1-star and 3-star reviews of incumbent tools. Skip 5-star (signal-poor for what's missing).
- Hacker News — keyword search, Ask HN + Show HN, read full comment threads.
- ProductHunt — competitor launch comments + adjacent products.
- Crunchbase — funding trends as investor-conviction proxy.
- Twitter/X — keyword + advanced search; favor threads over tweets.
B2B Enterprise add-ons
- Gartner Peer Insights, TrustRadius, LinkedIn Groups, PeerSpot.
Cybersecurity add-ons
- r/cybersecurity, r/netsec, Dark Reading, SecurityWeek, CyberScoop, CISO Series podcast notes, RSA/Black Hat session content, SANS Reading Room, PeerSpot.
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.
- 2d ago First seen · 123 lines · 75 tokens per session scan A 10f536c45fa7
community-mining is a skill published in the GitHub repository dormstern/forge (6 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 1,368 once invoked, about $0.0004 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.