research

research is a skill for Claude Code from TheWinci/mimirs. It costs 88 tokens per session (491 once invoked), scanned A, original, Apache-2.0.

A project-research skill for answering difficult questions by combining source code, project structure, version history, recorded decisions, and discussions.

In plain words
What is it for?
Use it for deep, cross-cutting investigations that require searching code, tracing relationships, checking history, and supporting conclusions with project sources.
Why use it?
It helps explain how a project works when the answer is spread across many files and past changes rather than documented in one place.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the mimirs plugin — 11 skills, 3 hooks shipped together

Good fit Use it for deep, cross-cutting investigations that require searching code, tracing relationships, checking history, and supporting conclusions with project sources.

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

Made for: Claude Code.

Or install mimirs, the plugin that ships this one along with the rest of its 11 skills, 3 hooks.

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/thewinci/mimirs/research/github.svg)](https://agentmods.dev/skills/thewinci/mimirs/research)
Your own site
<a href="https://agentmods.dev/skills/thewinci/mimirs/research"><img src="https://agentmods.dev/badge/skills/thewinci/mimirs/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/thewinci/mimirs/research"><img src="https://agentmods.dev/badge/skills/thewinci/mimirs/research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 491 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.00088 $0.00491
Opus 5.5 $0.00035 $0.00196
Sonnet 5.5 $0.00018 $0.00098
Haiku 4.5 $0.00009 $0.00049

Measured 2mo ago against content hash 804bfcf3673b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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 · 19 lines

What it actually says

Research

Goal: a thorough, cited answer to a specific question — pulled from across the whole project memory, not one file or one area. Where explore maps an area's structure, research answers a question by combining code, history, decisions, and discussion.

  1. Frame the question — break it into the sub-questions you must answer. State them, so the synthesis can be checked against them at the end.
  2. The code — search "<sub-question>" for the relevant files, then read_relevant "<behavior>" for the actual functions/sections with line ranges. Use the extensions/dirs/excludeDirs filters to scope. search_symbols <name> for named things you already know.
  3. How it connects — when the question is about relationships: project_map(focus: <file>), depends_on/dependents <file>, impact <symbol> (transitive callers), trace from=<a> to=<b> (how one reaches another).
  4. History & why — search_commits "<topic>" for why and when it changed; file_history <file> for how a file evolved.
  5. Decisions & discussion — search_checkpoints "<topic>" for recorded decisions and direction changes; search_conversation "<topic>" for the back-and-forth and alternatives considered.
  6. Caveats — get_annotations (search across notes) for known bugs, constraints, and fragile spots that qualify the answer.
  7. Verify — before asserting any claim, reopen the cited source and confirm it. Don't synthesize from snippets alone.

Finish: answer each sub-question in plain language with a file:line, commit, or checkpoint citation; separate what the source proves from what is inferred; list what stayed unresolved instead of guessing.

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. 2mo ago First seen · 19 lines · 88 tokens per session scan A 804bfcf3673b

Subscribe to this mod's changes

research is a skill published in the GitHub repository TheWinci/mimirs (30 stars, last pushed 18d ago), licensed Apache-2.0. It adds 88 tokens to every session and 491 once invoked, about $0.0004 per session on Opus 5.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

research compared with skills from other repositories

research next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
researchTheWinci/mimirsSkill3018d agoApache-2.0A88Claude Code
memorix-troubleshootingAVIDS2/memorixSkill906yesterdayApache-2.0A36Claude Code
researchstudy8677/repobrainSkill1.4k14d agoMITA32Claude Code
azure-event-grid-webhookshookdeck/webhook-skillsSkill98yesterdayMITA148Claude Code, Codex
formstack-webhookshookdeck/webhook-skillsSkill98yesterdayMITA108Claude Code, Codex
wordpress-com-webhookshookdeck/webhook-skillsSkill98yesterdayMITA160Claude Code, Codex
clio-webhookshookdeck/webhook-skillsSkill98yesterdayMITA64Claude Code, Codex