research

A project command that identifies missing information, creates focused research questions, and gathers knowledge from outside sources for a development task.

In plain words
What is it for?
Use it to research technical approaches, best practices, security concerns, performance issues, and alternatives while considering the project's architecture and technology stack.
Why use it?
It helps when the codebase does not contain enough information to make an implementation, security, performance, or design decision. The questions are prioritized and tied to decisions the task may require.

Command for Claude Code

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.

agentmods
npx agentmods add commands/brain-bootstrap/claude-code-brain-bootstrap/research
Clone the repo
git clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrap

Made for: Claude Code.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 612 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00612
Opus 5 $0.00005 $0.00306
Sonnet 5 $0.00002 $0.00122
Haiku 4.5 $0.00001 $0.00061

Measured 2d ago against content hash 599a824b668d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

.claude/commands/research.md · 79 lines

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 and gather knowledge about: $ARGUMENTS

ultrathink — use extended reasoning for question formulation and knowledge synthesis.

Context

Read CLAUDE.md for project architecture and conventions. Read claude/architecture.md for the tech stack.

Instructions

Phase 1: Analyze Information Gaps

Based on $ARGUMENTS and the project context:

  1. Identify what you already know from the codebase
  2. Identify knowledge gaps where external information would be valuable
  3. Categorize gaps: technical implementation, best practices, security, performance, alternatives

Phase 2: Generate Targeted Research Questions

Generate 5-7 focused research questions that are:

  • Specific — target a distinct piece of information, not general knowledge
  • Actionable — the answer should directly inform a design or implementation decision
  • Prioritized — most critical questions first
  • Diverse — cover different aspects (implementation patterns, pitfalls, performance, security)

Example questions:

  • "What are the current best practices for [specific pattern] in [framework version]?"
  • "What are common pitfalls when integrating [library A] with [library B]?"
  • "How does [approach A] compare to [approach B] for [specific use case] in terms of performance and maintainability?"

Phase 3: Research

For each question:

  1. Check the codebase first — grep for existing patterns, read relevant files
  2. Check project docsclaude/*.md may already have the answer
  3. If MCP web search is available (check .mcp.json): use mcp__SERVER_KEY__search to find current information
  4. If no web search: use your training knowledge, clearly marking confidence levels

Phase 4: Synthesize Findings

Present findings as a structured report:

## Research Report: [Topic]

### Question 1: [Question]
**Confidence:** [High/Medium/Low]
**Finding:** [Concise answer]
**Source:** [Codebase pattern / MCP search / Training knowledge]
**Recommendation:** [Actionable next step]

### Question 2: ...

Read the full file on GitHub · 79 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.

  1. 2d ago First seen · 79 lines · 11 tokens per session scan A 599a824b668d

Subscribe to this mod's changes

research is a command published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 612 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-30.