research

A research workflow that breaks a question into smaller parts, gathers information from several sources, and combines the findings into a sourced report.

In plain words
What is it for?
Use it to investigate topics, analyse trends, check current events, or gather comprehensive information from multiple sources.
Why use it?
It avoids handling many searches one at a time and helps organise broad or current questions into a single response with confidence levels.

Skill for Claude CodeCodex

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 skills/danielmiessler/paiplugin/research
Any agent
npx skills add danielmiessler/PAIPlugin --skill research
Clone the repo
git clone --depth 1 https://github.com/danielmiessler/PAIPlugin

Made for: Claude Code, Codex.

Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 328 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.00076 $0.00328
Opus 5 $0.00038 $0.00164
Sonnet 5 $0.00015 $0.00066
Haiku 4.5 $0.00008 $0.00033

Measured 2d ago against content hash db673989ec26, 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.

skills/research/SKILL.md · 41 lines

What it actually says

Research Skill

When to Use This Skill

This skill activates when the user requests research or information gathering:

  • "Do research on X"
  • "Research this topic"
  • "Find information about X"
  • "Investigate this subject"
  • "Analyze trends in X"
  • "Current events research"
  • Any comprehensive information gathering request

How to Execute

Execute the /conduct-research slash command, which handles the complete workflow:

  1. Decomposing research questions into 3-10 sub-questions
  2. Launching up to 10 parallel research agents (perplexity, claude, gemini)
  3. Collecting results in 15-30 seconds
  4. Synthesizing findings with confidence levels
  5. Formatting comprehensive report with source attribution

Available Research Agents

  • All agents with "researcher" in their name in the agents directory.

Speed Benefits

  • Old approach: Sequential searches → 5-10 minutes
  • New approach: 10 parallel agents → Under 1 minute

Full Workflow Reference

For complete step-by-step instructions: read ${PAI_DIR}/commands/conduct-research.md

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 · 41 lines · 76 tokens per session scan A db673989ec26

Subscribe to this mod's changes

research is a skill published in the GitHub repository danielmiessler/PAIPlugin (56 stars, last pushed 9mo ago), licensed MIT. It adds 76 tokens to every session and 328 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens