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 n24q02m/wet-mcp --skill research-topicgit clone --depth 1 https://github.com/n24q02m/wet-mcpWrote 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/wet-mcp/research-topic)<a href="https://agentmods.dev/skills/n24q02m/wet-mcp/research-topic"><img src="https://agentmods.dev/badge/skills/n24q02m/wet-mcp/research-topic/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/n24q02m/wet-mcp/research-topic"><img src="https://agentmods.dev/badge/skills/n24q02m/wet-mcp/research-topic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.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 10d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- research-topic — 100% identical, 0 lines differ
- research-topic — 100% identical, 0 lines differ
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.
- 10d ago First seen · 83 lines · 68 tokens per session scan A 253c4689d3bd
research-topic is a skill published in the GitHub repository n24q02m/wet-mcp (17 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
knowledge-audit
Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.
temporal-query
Answer time-travel questions over stored memory — what was believed at a past point in time, when a belief changed, and what replaced it. Use when the user says "as of", "back in", "at the time", "history of", "timeline", "what did I think then", or asks why a current memory contradicts an older one.
memory-commit
Use when the user explicitly says "remember this", "save this", "ghi nho", "luu lai", "save for next time", or otherwise asks to persist the immediately preceding context. Captures with the appropriate contexttype (decision, preference, fact, skill, task, conversation) so future sessions can retrieve it accurately.
recall-context
Use at session start, before significant decisions, or when a new task references a known project to recall mnemo memories matching the current working directory, recently edited files, or topic keywords. Helps maintain continuity across sessions and avoid redoing past research.
session-handoff
End-of-session knowledge capture — decisions, preferences, corrections, conventions, open questions.
passport-bootstrap
Use when the user installs mnemo-mcp on a fresh machine and wants to restore prior memory state from S3 or Google Drive (Phase 2 passport sync). Triggers on phrases like "set up mnemo on this machine", "restore my memory passport", "import passport", "bootstrap mnemo", or when the user says they got a new laptop / VM…