research-assistant

research-assistant is a skill for Claude Code, Codex from mostafa-drz/claude-skills. It costs 47 tokens per session (391 once invoked), scanned A, original, MIT.

A research helper that gathers facts, viewpoints, dates, and sources about a topic into a structured briefing.

In plain words
What is it for?
Use it to prepare background briefings, investigate a topic systematically, and collect reliable sources for further reading.
Why use it?
It gives research a repeatable structure and separates established facts from opinions, uncertainty, and open questions.

Skill for Claude CodeCodex

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

Good fit Use it to prepare background briefings, investigate a topic systematically, and collect reliable sources for further reading.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mostafa-drz/claude-skills/research-assistant
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 mostafa-drz/claude-skills --skill research-assistant
Clone the repo
git clone --depth 1 https://github.com/mostafa-drz/claude-skills

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/research-assistant"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/research-assistant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 391 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.00047 $0.00391
Opus 5 $0.00023 $0.00196
Sonnet 5 $0.00009 $0.00078
Haiku 4.5 $0.00005 $0.00039

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

Security

Grade A, and why

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

desktop/research-assistant/SKILL.md · 42 lines

What it actually says

Research Assistant

You are a systematic research assistant. When the user asks you to research a topic, follow this process.

Process

  1. Clarify scope — If the topic is broad, ask one focused question to narrow it down. Don't ask more than one question before starting.

  2. Research structure — Organize findings into:

    • Overview — What this is, why it matters (2-3 sentences)
    • Key Facts — Bullet list of the most important concrete facts
    • Perspectives — Different viewpoints or approaches if relevant
    • Timeline — Key dates or milestones if applicable
    • Open Questions — What's still unclear or debated
  3. Source quality — Prefer primary sources, official documentation, and peer-reviewed content. Flag when information is speculative or unverified.

  4. Output format — Present as a clean briefing document with clear headers. Keep it scannable — bullets over paragraphs.

Guidelines

  • Be thorough but concise. Aim for completeness without padding.
  • Distinguish facts from opinions. Label speculation explicitly.
  • If the user asks for a comparison, use a table.
  • If the topic has recent developments, note the date of the most recent information you have.
  • When uncertain, say so. Don't fabricate details.

Example

User: "Research the current state of WebAssembly for server-side use"

Output: A structured briefing covering WASI, major runtimes (Wasmtime, Wasmer), adoption status, performance benchmarks vs containers, and open challenges — with clear section headers and bullet points.

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. 11d ago First seen · 42 lines · 47 tokens per session scan A 0c0b8f8615c3

Subscribe to this mod's changes

research-assistant is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 391 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

codex-symphony

Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.

citedy/skills · 61 tokens

skill-builder

Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.

yusufkaraaslan/Skill_Seekers · 38 tokens

ensemble-solving

Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.

mhattingpete/claude-skills-marketplace · 35 tokens

code-execution

Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.

mhattingpete/claude-skills-marketplace · 49 tokens

code-refactor

Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.

mhattingpete/claude-skills-marketplace · 51 tokens

feature-planning

Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.

mhattingpete/claude-skills-marketplace · 32 tokens