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/n24q02m/claude-plugins/research-topicnpx skills add n24q02m/claude-plugins --skill research-topicgit clone --depth 1 https://github.com/n24q02m/claude-pluginsWrote 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/n24q02m/claude-plugins/research-topic)<a href="https://agentmods.dev/skills/n24q02m/claude-plugins/research-topic"><img src="https://agentmods.dev/badge/skills/n24q02m/claude-plugins/research-topic.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 | $0.00068 | $0.00808 |
| Opus 5 | $0.00034 | $0.00404 |
| Sonnet 5 | $0.00014 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
research-topic 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 5d 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.
This is a copy
100% identical to research-topic — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
research-topic
Drive wet-mcp's extract(action="agent") to answer a research question
end to end: one search round + concurrent extracts of the top hits + a
single LLM synthesis pass that preserves numbered [N] citations
matching the returned sources.
Use this skill when:
- The user asks an open-ended question that needs multiple sources.
- "Summarise the current state of X."
- "What's the latest on Y?"
- "Compare approaches to Z."
- The user needs a quoted, cited answer (the citations are first-class output, not an afterthought).
Do NOT use this skill when:
- The user already gave you a specific URL -- call
extract(action="extract"). - The user wants a single search result list -- call
search(action="web"). - The question is about library API documentation -- call
search(action="docs_query")against a Tier 1 / locked stack.
Steps
-
Restate the question to the user in 1-2 sentences (calibration: confirm scope before spending tokens).
-
Pick
max_urlsbased on breadth:- 3-5 for a tight question (single technology, single timeframe).
- 6-10 for a broad survey (multiple competitors, multi-year window).
- Hard ceiling is 20 (cost guard).
-
Pick
synthesis_modelonly if the user asked for a specific model. Otherwise omit and let wet auto-detect fromLLM_MODELS/GEMINI_API_KEY/OPENAI_API_KEY/XAI_API_KEY. -
Call
extract(action="agent", query="<question>", max_urls=<N>)Optional knobs:
synthesis_model="...",token_budget=<int>(default 10000; raise for long-form questions, lower for tight cost control). -
Quote the synthesised Markdown verbatim to the user, then list the sources from the
sourcesarray as clickable URLs. Ifper_url_metadatashows anyerror, mention which URL failed and that the synthesis used the remaining N-K sources. -
If wet returns
Error: no LLM provider detected, surface the exact error to the user (do not silently retry againstsearch(action="research")); they need to set one of the supported API keys before agent works.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 83 lines · 68 tokens per session scan A 253c4689d3bd
research-topic is a skill published in the GitHub repository n24q02m/claude-plugins (4 stars, last pushed today), licensed Apache-2.0. It adds 68 tokens to every session and 808 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to research-topic, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
persona-triggers
페르소나 v5 트리거 상세(AT 20패턴 + 15관점 매핑·매칭 예시). 관점·객관적·철저·깊이·검증·추천·디버깅·방향·진행·근거·출처·사례·팩트·증거 등 트리거 단어 감지 시 상세 참조.
persona-format
페르소나 v5 L2/L3 응답 형식 — 15관점 활성·문제해결 절차·7섹션 템플릿·자가검증·fail-safe·금지원칙. 코드 변경·디버깅·구현 등 L2/L3 작업 시 로드.
persona-accountant
15년+ 회계·세무 전문가 페르소나(#14) 깊은 도메인. 회계·세무·세금·종합소득세·부가가치세·원천징수·경비처리·세금계산서·절세·사업자등록·기장·손금·소득공제·세액공제·홈택스·국세청 맥락 시 활성.
persona-marketer
15년+ 마케팅·세일즈 전문가 페르소나(#15) 깊은 도메인. 마케팅·세일즈·카피·콘텐츠·SEO·광고·랜딩페이지·전환·퍼널·브랜딩·포지셔닝·리드·캠페인·리텐션·그로스·어카운트·컨설팅 맥락 시 활성.
persona-safety
페르소나 v5 안전 작업 — 보안 always-on·비가역 작업 게이트·코드 메타규칙·모바일 UI(375px) 검증·외부도구 도입검토. 코드/UI/보안/배포/삭제/force push 작업 시 로드.
persona-lawyer
15년+ 전문 변호사 페르소나(#11) 깊은 도메인. 법률·계약·면책·규제·약관·audit·자본시장법·GDPR·개인정보·저작권·라이선스·AML·컴플라이언스 맥락 시 활성.