agentmods.dev

research

research is a skill for Claude Code from paulo-yamagishi/claude-code-setup. It costs 17 tokens per session (444 once invoked), scanned A, original, MIT.

A research workflow for Claude Code, an AI coding assistant, that combines official documentation with community sources and existing repository content. It organizes findings into verified information, practical tips, and gaps.

In plain words
What is it for?
Use it to investigate topics such as hooks, plugins, or model settings, check the current official guidance, search discussions and tutorials, and compare the results with project documentation.
Why use it?
Claude Code features and configuration details can change, while community advice may be incomplete or unofficial. Comparing sources helps separate documented behavior from suggestions and missing coverage.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

not rated 2repo 7mo ago A scan 17 tokens original MIT

Good fit Use it to investigate topics such as hooks, plugins, or model settings, check the current official guidance, search discussions and tutorials, and compare the results with project documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/paulo-yamagishi/claude-code-setup/research
View source ↗ paulo-yamagishi/claude-code-setup
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.

Any agent
npx skills add paulo-yamagishi/claude-code-setup --skill research
Clone the repo
git clone --depth 1 https://github.com/paulo-yamagishi/claude-code-setup

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.

agentmods badge for research

README.md
[![agentmods](https://agentmods.dev/badge/skills/paulo-yamagishi/claude-code-setup/research/github.svg)](https://agentmods.dev/skills/paulo-yamagishi/claude-code-setup/research)
Your own site
<a href="https://agentmods.dev/skills/paulo-yamagishi/claude-code-setup/research"><img src="https://agentmods.dev/badge/skills/paulo-yamagishi/claude-code-setup/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.

agentmods 80×15 button for research

Your own site · 80×15
<a href="https://agentmods.dev/skills/paulo-yamagishi/claude-code-setup/research"><img src="https://agentmods.dev/badge/skills/paulo-yamagishi/claude-code-setup/research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 444 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00444
Opus 5 $0.00009 $0.00222
Sonnet 5 $0.00003 $0.00089
Haiku 4.5 $0.00002 $0.00044

Measured 9d ago against content hash 70e5e7551fa9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 9d 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/skills/research/SKILL.md · 47 lines

What it actually says

Research

Research a Claude Code topic using official docs and community sources, then integrate verified findings.

Steps

  1. Parse topic: Use $ARGUMENTS as the research topic (e.g., "hooks", "plugins", "model configuration").

  2. Fetch official docs:

    • WebFetch https://docs.anthropic.com/en/docs/claude-code and navigate to the relevant section
    • Extract current official information about the topic: features, config format, options, limitations

  3. Search community sources:

    • WebSearch for: "claude code" $ARGUMENTS site:reddit.com — recent discussions and tips
    • WebSearch for: "claude code" $ARGUMENTS — blog posts, tutorials, announcements
    • Extract actionable tips, undocumented patterns, and real-world usage insights

  4. Read existing repo content:

    • Grep for $ARGUMENTS across core/, projects/, skill/, .claude/skills/ to find what we already cover
    • Read the most relevant files to understand current state of our documentation

  5. Cross-reference and classify findings into three sections:

    Confirmed new info — Information verified against official docs that is not yet in our guides. Include source URL.

    Community tips — Plausible patterns from real usage not found in official docs. Mark each as [UNVERIFIED]. Include source URL.

    Outdated content in our repo — Anything in our guides that contradicts current official docs. Include file path and line number.

  6. Present report to the user with the three sections above.

  7. Ask user which findings to integrate, then update the relevant core/ or projects/ files accordingly.

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. 9d ago First seen · 47 lines · 17 tokens per session scan A 70e5e7551fa9

Subscribe to this mod's changes

research is a skill published in the GitHub repository paulo-yamagishi/claude-code-setup (2 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 444 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.

Research
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

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 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

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens