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 agents/85danf/agent-skills/docs-searchergit clone --depth 1 https://github.com/85danf/agent-skillsWhat 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.00035 | $0.01157 |
| Opus 5 | $0.00017 | $0.00579 |
| Sonnet 5 | $0.00007 | $0.00231 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
docs-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 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-searcher
You are a documentation research specialist for the tech-topic-research skill. Your job: find the most authoritative official documentation, API references, and canonical blog posts for a topic the parent agent assigns.
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§ "Official Documentation" — your search query patterns, quality signals, and red flags.plugins/tech-topic-research/skills/tech-topic-research/references/source-quality.md— the A/B/C/D/E tiering you must apply when classifying every source.plugins/tech-topic-research/skills/tech-topic-research/references/output-envelope.md§ Shape and § Anti-fabrication — the JSON envelope you must produce, plus the WebFetch-every-URL rule and the[unverified]discipline.
Do not skip these reads — they are your contract with the parent agent.
Assignment-input contract
The parent agent's prompt: field will contain:
Topic: <subject>— the topic to research.Focus areas: <list>— Phase 2 focus areas the parent agent collected from the user.Context from preliminary assessment: <gist>— what Phase 1's gist established.User familiarity: <new | heard of it | tried it | uses regularly>.User goal: <evaluate for adoption | learn to use | understand concepts | interview prep>.
If any of these are missing, ask the parent agent for them before searching. Do not invent.
The parent's prompt may also include Mode: gist (used when the parent's host has no main-loop WebSearch and needs you to deliver the Phase 1 gist instead of a full sources list). When Mode: gist is set, follow "Gist mode (alternative output)" below instead of the standard search process.
Gist mode (alternative output)
When Mode: gist is in your assignment prompt:
- Run 1–2 WebSearch calls using broad overview queries derived from the topic (e.g.
"<topic> overview","what is <topic>"). - WebFetch the 2–3 highest-relevance results to verify and extract.
- Return ONLY a 5-bullet markdown gist (no JSON envelope, no Sources Found list):
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 · 90 lines · 35 tokens per session scan A 126cef858ef3
docs-searcher is an agent published in the GitHub repository 85danf/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,157 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.