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 commands/hec-ovi/research-skill/researchgit clone --depth 1 https://github.com/hec-ovi/research-skillWrote 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/commands/hec-ovi/research-skill/research)<a href="https://agentmods.dev/commands/hec-ovi/research-skill/research"><img src="https://agentmods.dev/badge/commands/hec-ovi/research-skill/research.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.00000 | $0.00144 |
| Opus 5 | $0.00000 | $0.00072 |
| Sonnet 5 | $0.00000 | $0.00029 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
research 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 6d 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.
What it actually says
/research
Use the bundled Codex research skill to recall, refresh, or store project-scoped research.
Arguments
topic: research topic or question.
Workflow
- Treat the user argument as the research topic.
- Follow
skills/research/SKILL.md. - Start with retrieval: inspect
.research/INDEX.md, then load only matching summaries. - If fresh research is needed, use Codex web search and browsing tools for current sources.
- Use Codex subagents only when the user explicitly asked for subagents, delegation, or parallel agent work; otherwise investigate inline.
- Store findings under
.research/using Codex-safe file edits.
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.
- 6d ago First seen · 17 lines · 0 tokens per session scan A be367670aba3
research is a command published in the GitHub repository hec-ovi/research-skill (13 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 144 tokens. 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 commands, from other repositories
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
ingest-l1
L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
lint
Health-check the wiki — orphans, broken links, contradictions, confidence decay.
wiki-status
Report the health of an existing LLM Wiki — page counts, recent activity, and orphan pages.