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 research-project-orientergit 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/research-project-orienter)<a href="https://agentmods.dev/skills/wenyuchiou/research-hub/research-project-orienter"><img src="https://agentmods.dev/badge/skills/wenyuchiou/research-hub/research-project-orienter/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/wenyuchiou/research-hub/research-project-orienter"><img src="https://agentmods.dev/badge/skills/wenyuchiou/research-hub/research-project-orienter.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.00091 | $0.01043 |
| Opus 5 | $0.00046 | $0.00522 |
| Sonnet 5 | $0.00018 | $0.00209 |
| Haiku 4.5 | $0.00009 | $0.00104 |
Grade A, and why
research-project-orienter 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 11d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
research-project-orienter
Quickly orient an AI assistant inside a research workspace without
scanning the whole repository. Reads the .research/ manifest files
written by research-context-compressor and produces a single
in-conversation orientation memo.
Part of the research-hub skill pack; works alongside Zotero, Obsidian, and NotebookLM workflows but does not require any of them.
This skill is fast and read-only. If .research/ doesn't exist yet,
defer to research-context-compressor first.
When to use
Trigger phrases:
- "Understand this research project before helping me."
- "Summarize this repo's research question, data, experiments, and outputs."
- "Build a context map for this paper/project."
- "Orient me in this codebase."
- "What is this repo about?"
Not for:
- Detailed code review — that's a code task.
- Generating new manifests — use
research-context-compressorfirst. - Literature review — use
literature-triage-matrix.
Inputs
Read in this order:
.research/project_manifest.yml— top-level orientation. Required..research/experiment_matrix.yml— experiment status. Read if present..research/data_dictionary.yml— datasets. Read if present..research/decisions.md— recent ADRs. Read last 5 if present..research/open_questions.md— known unknowns. Read all..research/run_log.md— last 3 entries for context.
Do not read source code, data files, or PDFs unless the manifest points you at a specific path AND the user's question requires it.
What if .research/ doesn't exist?
Tell the user:
This project doesn't have a
.research/manifest yet. I can create one first (loadsresearch-context-compressorskill, takes ~30 seconds and writes 3 small YAML files), or I can fall back to scanning the repo directly (slower, more tokens). Which?
Don't auto-fall-back — ask first. If they pick "scan", read README.md +
docs/ + the top-level entrypoint, and produce the memo from that, but
caveat: "this orientation came from a one-shot scan; for more reliable
future sessions, run research-context-compressor once."
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.
- 11d ago First seen · 122 lines · 91 tokens per session scan A 88e83220d4f0
research-project-orienter is a skill published in the GitHub repository WenyuChiou/research-hub (54 stars, last pushed 3d ago), licensed MIT. It adds 91 tokens to every session and 1,043 once invoked, about $0.0005 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
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.