agentmods.dev

research

research is a skill for Claude Code, Codex from nguyenvanduocit/research-kit. It costs 49 tokens per session (925 once invoked), scanned A, original, from a forked repository, MIT.

A workflow coordinator for systematic research, meaning a planned process for investigating a question and recording evidence. It checks the current research files and identifies the next stage.

In plain words
What is it for?
It helps continue research through stages such as defining the question, planning methods, creating tasks, collecting data, analysing findings, and writing conclusions.
Why use it?
It removes the need to track research progress and choose the next command manually.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 20repo 5mo ago A scan 49 tokens fork MIT

Good fit It helps continue research through stages such as defining the question, planning…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nguyenvanduocit/research-kit/research
View source ↗ nguyenvanduocit/research-kit
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 nguyenvanduocit/research-kit --skill research
Clone the repo
git clone --depth 1 https://github.com/nguyenvanduocit/research-kit

Made for: Claude Code, Codex.

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/nguyenvanduocit/research-kit/research.svg)](https://agentmods.dev/skills/nguyenvanduocit/research-kit/research)
Your own site
<a href="https://agentmods.dev/skills/nguyenvanduocit/research-kit/research"><img src="https://agentmods.dev/badge/skills/nguyenvanduocit/research-kit/research.svg" alt="Measured on agentmods" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 925 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 fork From a forked repository.
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.00049 $0.00925
Opus 5 $0.00024 $0.00463
Sonnet 5 $0.00010 $0.00185
Haiku 4.5 $0.00005 $0.00093

Measured 7d ago against content hash 76af7d67e74a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 7d 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.

templates/skills/research/SKILL.md · 104 lines

How it starts

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

research

SRD orchestrator that detects research state and drives it forward.

Quick start

  1. Detect current branch and research directory
  2. Scan for existing artifacts to determine phase
  3. Present state and suggest next step
  4. Execute via the appropriate slash command

Detect state

Check environment:

  1. git rev-parse --abbrev-ref HEAD 2>/dev/null → if branch matches ###-topic-name, research dir is research/<branch-name>/
  2. If on main, check research/ for topic directories
  3. Fallback: RESEARCH_TOPIC env var

Scan artifacts in research directory:

File Phase complete
definition.md Define
methodology.md Methodology
tasks.md Task breakdown
execution.md + data/ files Execution
analysis.md Analysis
synthesis.md Synthesis
publications/ files Publication

Phase transitions

NO research dir     → Ask topic, then /research.define
definition.md only  → /research.methodology
methodology.md      → /research.tasks (or /research.refine if unclear)
tasks.md            → /research.execute
execution.md + data → /research.analyze
analysis.md         → /research.synthesize
synthesis.md        → /research.publish
publications/       → Complete. Ask if revisions needed.

Execution

Present detected state before acting:

Current research: [topic]
Phase completed: [last phase]
Next step: [action]

Wait for user confirmation, then invoke the slash command. After completion, suggest next phase.

Agent delegation:

  • @agent-literature-specialist → methodology/execution phases (source discovery)
  • @agent-data-collector → execution phase (data gathering)
  • @agent-analysis-expert → analysis phase (statistical work)
  • @agent-academic-writer → publish phase (writing)
  • @agent-research-reviewer → phase transitions (quality validation)

Quality gates

Every phase transition is enforced by quality gates at two layers:

  1. Shell scripts check structural requirements (file existence, sections, content size, source counts). Failures block the setup script with clear error messages.
  2. Commands instruct AI to verify content quality (specificity, coverage, evidence standards). AI outputs gate results and stops if REQUIRED checks fail.

Read the full file on GitHub · 104 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. 7d ago First seen · 104 lines · 49 tokens per session scan A 76af7d67e74a

Subscribe to this mod's changes

research is a skill published in the GitHub repository nguyenvanduocit/research-kit (20 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 925 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.

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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 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

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