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 WenyuChiou/research-hub --skill skillgit clone --depth 1 https://github.com/WenyuChiou/research-hubWrote 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/wenyuchiou/research-hub/skill)<a href="https://agentmods.dev/skills/wenyuchiou/research-hub/skill"><img src="https://agentmods.dev/badge/skills/wenyuchiou/research-hub/skill.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.00075 | $0.00716 |
| Opus 5 | $0.00037 | $0.00358 |
| Sonnet 5 | $0.00015 | $0.00143 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
research-hub 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.
This is a copy
100% identical to research-hub — 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
research-hub
research-hub is an AI-operable research workspace. It can use Zotero, Obsidian, and NotebookLM together, but it is also useful when the user only has two of them.
Default language policy: respond in the user's language, but generate durable research notes and metadata in English unless the user asks otherwise.
Choose The Workflow
| User has | Prefer this path |
|---|---|
| Zotero + Obsidian + NotebookLM | Full research-hub auto "topic" workflow |
| Zotero + Obsidian | Search/add/backfill papers, write Markdown notes, skip NotebookLM with --no-nlm |
| Obsidian + NotebookLM | import-folder, dashboard, NotebookLM bundle/upload/generate |
| Zotero + NotebookLM | Zotero-backed paper selection and NotebookLM operations |
| No accounts yet | research-hub dashboard --sample |
First Commands
research-hub dashboard --sample
research-hub setup
research-hub auto "topic" --no-nlm
research-hub serve --dashboard
research-hub doctor --autofix
For local files without Zotero:
research-hub setup --persona analyst
research-hub import-folder ./papers --cluster my-local-review
research-hub serve --dashboard
AI Host Integration
For MCP hosts, configure:
{ "mcpServers": { "research-hub": { "command": "research-hub", "args": ["serve"] } } }
Install host-specific skill files when useful:
research-hub install --platform claude-code
research-hub install --platform cursor
research-hub install --platform codex
research-hub install --platform gemini
For Hermes, OpenClaw, or other hosts with SKILL.md/rules support,
copy the relevant skills/<name>/ directories manually or inline the
skill text into the host's instructions. Use MCP/REST for tool calls
when no installer target exists.
Operating Rules
- Run
research-hub doctorfirst when setup or runtime behavior is unclear. - Use
--no-nlmfor smoke tests or when NotebookLM browser automation is not configured. - Prefer
import-folderfor analysts, internal knowledge bases, local PDFs, DOCX, Markdown, TXT, and URL sources. - Prefer Zotero-backed commands for DOI/arXiv-heavy academic literature workflows.
- Do not delete clusters without previewing cascade impact first.
- Treat the vault as user-owned local data; avoid overwriting notes unless the user explicitly asks.
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 · 79 lines · 75 tokens per session scan A 0eb822aa2126
research-hub is a skill published in the GitHub repository WenyuChiou/research-hub (54 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 716 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to research-hub, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
migrate-v0-to-v1
Migrate a Scraps wiki from v0 to v1. Use this whenever the user asks to upgrade Scraps, migrate v0 wiki syntax/config, convert implicit tags to explicit #[[tag]], move from scraps-writer to scraps, or audit a wiki for v1 readiness. This skill is designed for one-pass LLM-led migrations that discover the latest v0 and…
remem
Use when the user asks Codex to recall prior project context, save durable decisions or bug fixes, inspect remem memory health, or activate remem automatic memory hooks from the Codex plugin.
ingest
Create a new scrap from a source (prompt, URL, or arbitrary markdown), update cross-links in related scraps, and run a sanity check. Use this when the user wants to add a scrap, summarize an article, save synthesized content to the wiki, or file back a Q&A result.
query
Answer questions about the wiki by searching, reading, and synthesizing relevant scraps with [[Title]] citations. Use this when the user wants to query the wiki, ask what they have written about a topic, compare scraps, find related notes, or pull a synthesized overview from existing scraps.
planning-with-scratchpad
Use when user explicitly requests planning with a scratchpad, or asks for persistent tracking of a complex task that the human can browse visually. Backs planning files with the scratch CLI so a pad's files are registered and viewable.
scratch
Organize knowledge from an agent session into a scratchpad — a folder of files plus a scratchpad.json manifest. Use when a task generates notes, snippets, command output, diagrams, or artifacts worth keeping together for a session/activity.