A guided research command that combines notes from a local knowledge store with web research, then saves a cited note.

Use it to investigate a topic, verify current information online, and create a source-backed note for future work.

It reduces the work of deciding what to search, checking sources, and recording findings. Later research can build on notes captured earlier.

research — Command for Claude Code by ethanaubuchon

Install

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.

Clone the repo

git clone --depth 1 https://github.com/ethanaubuchon/dossier-tradecraft

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ethanaubuchon/dossier-tradecraft/research/github.svg)](https://agentmods.dev/commands/ethanaubuchon/dossier-tradecraft/research)

Your own site

<a href="https://agentmods.dev/commands/ethanaubuchon/dossier-tradecraft/research"><img src="https://agentmods.dev/badge/commands/ethanaubuchon/dossier-tradecraft/research/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ethanaubuchon/dossier-tradecraft/research"><img src="https://agentmods.dev/badge/commands/ethanaubuchon/dossier-tradecraft/research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,249 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00023	$0.01249
Opus 5	$0.00012	$0.00624
Sonnet 5	$0.00005	$0.00250
Haiku 4.5	$0.00002	$0.00125

Measured 11d ago against content hash ec0711d4c18a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 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.

commands/research.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are starting a research session. The topic (if provided): $ARGUMENTS

This is the /research recipe (Phase 1 v2) of the dossier-tradecraft framework.

Principles

Vault = grounding, not a research target. The vault sweep enriches context for the web step; it is not presented alongside web findings as a parallel source.
Web = primary research target, always runs. Model priors can't be trusted for fast-moving or landscape topics.
Frame step is near-zero. Topic-as-stated passes through. Clarifications are conditional, not mandatory.
Capture is agent-judged; write directly. You pick the slug, draft the note with citations, and write it. Surface what was captured afterward — the user can redirect, revise, or ask you to move/edit the note post-hoc. Anchor is a capture-time output, not a frame-time input.
Loop iteration is context-accretive. Each turn builds on previous turn's captures.
Thin caller. Cross-verify mechanics — cohort discipline, source-type annotations, used / marketplace consent gates, low retail-sample escalation — live in agents/web-researcher.md and skills/dispatch-exploration/SKILL.md. This recipe never re-implements them. Recipe-specific responsibilities are intake, loop shape, and capture; everything else is delegated.

Workflow

Load context — invoke the load-context skill (vault grounding pre-step).
Intake. If $ARGUMENTS is empty, ask what the user wants to research. Otherwise acknowledge the topic briefly and proceed. Do not interrogate scope, anchor, or biases up front.
Pre-vault clarify (conditional). Skip unless the topic is genuinely ambiguous. Fire only when:
- A term has multiple common meanings and the right one isn't obvious from context
- The user mentions known candidates without specifying skim-worthy vs. deep-dive
- Scope is truly unclear (landscape scan vs. narrow comparison vs. how-to-build)
Default: skip. When in doubt, don't ask.
Vault grounding. Invoke dispatch-exploration with 1–3 vault queries (target: vault) scoped to what's likely to enrich the web step — the user's rig, prior thinking, related projects. Present the compressed findings briefly; frame them as context for the web search, not the research output.

Read the full file on GitHub · 62 lines

Changes

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 · 62 lines · 23 tokens per session scan A ec0711d4c18a

Subscribe to this mod's changes

research is a command published in the GitHub repository ethanaubuchon/dossier-tradecraft (3 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 1,249 once invoked, about $0.0001 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-31.

Claude Code Research agentic-workflows claude claude-skills developer-tools knowledge-management

reflect

Reflect on recent work — log lessons to the journal and propose distilled rule updates for review.

Michael-OvO/obsidian-knowledge-agent · 17 tokens

doctor

Check vault health — broken links, orphans, missing frontmatter, MISSING placeholders — and propose fixes.

Michael-OvO/obsidian-knowledge-agent · 21 tokens

session-start

Thin wrapper (GETSITREP-10) — orientation logic (reading MANIFEST.md/STATUSREPORT.md/PROJECTPLAN.md/.sitrep-data.json, building the summary) lives entirely in getsitrep session-start. This file's only job is to invoke it and show the result — it does not re-read those files or re-derive the summary itself.

viitorohit/sitrep · 0 tokens

research