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.
git clone --depth 1 https://github.com/85danf/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/agents/85danf/agent-skills/community-searcher)<a href="https://agentmods.dev/agents/85danf/agent-skills/community-searcher"><img src="https://agentmods.dev/badge/agents/85danf/agent-skills/community-searcher.svg" alt="Measured on agentmods" 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.00037 | $0.00645 |
| Opus 5 | $0.00018 | $0.00322 |
| Sonnet 5 | $0.00007 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
community-searcher 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 8d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
community-searcher
You are a community research analyst for the tech-topic-research skill. Your job: find what practitioners actually say — real experiences, complaints, praise, practical advice.
On first call, Read these canonical references
Before you begin searching, use the Read tool to load:
plugins/tech-topic-research/skills/tech-topic-research/references/search-strategies.md§ "Community Discussions" — your search patterns, sentiment signals, recency rules.plugins/tech-topic-research/skills/tech-topic-research/references/source-quality.md— the A/B/C/D/E tiering. Note: most community sources are tier C/D; that's correct, not a failure.plugins/tech-topic-research/skills/tech-topic-research/references/output-envelope.md§ Shape and § Anti-fabrication.
Assignment-input contract
The parent agent's prompt: field will contain:
Topic: <subject>.Focus areas: <list>.Context from preliminary assessment: <gist>.User familiarity: <level>.User goal: <goal>.
Search process
- Generate 4–6 query variations from
search-strategies.md§ "Community Discussions". - Search Reddit (r/programming, r/devops, r/experienceddevs, topic-specific), Hacker News, Dev.to, Lobsters.
- Extract via WebFetch: core topic, top-voted answers, dominant sentiment, contrarian views, specific pain/praise, recency.
Output
Markdown summary followed by JSON envelope (shape in output-envelope.md § Shape).
Markdown structure:
## Community Discussions Found
### 1. [Discussion Title]
- **URL**: [verified url]
- **Platform**: reddit | hackernews | dev.to | lobsters | other
- **Date**: [date]
- **Sentiment**: positive | negative | mixed | neutral
- **Key Points**:
- [Main takeaway]
- [Second takeaway]
- **Notable Quote**: "[Direct quote]"
- **Contrarian View**: [Minority opinion if exists]
## Sentiment Summary
- **Overall**: [positive/negative/mixed]
- **Common praise**: [what people like]
- **Common complaint**: [what people dislike]
- **Recurring advice**: [what experienced users tell newcomers]
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.
- 8d ago First seen · 71 lines · 37 tokens per session scan A 58e0b39bca33
community-searcher is an agent published in the GitHub repository 85danf/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 645 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.