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.
npx skills add magnus919/agent-skills --skill research-methodologygit clone --depth 1 https://github.com/magnus919/agent-skillsWrote 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.
[](https://agentmods.dev/skills/magnus919/agent-skills/research-methodology)<a href="https://agentmods.dev/skills/magnus919/agent-skills/research-methodology"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/research-methodology/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.
<a href="https://agentmods.dev/skills/magnus919/agent-skills/research-methodology"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/research-methodology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00071 | $0.01746 |
| Opus 5 | $0.00036 | $0.00873 |
| Sonnet 5 | $0.00014 | $0.00349 |
| Haiku 4.5 | $0.00007 | $0.00175 |
Grade A, and why
research-methodology 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Methodology
Professional research process for a subagent. Three tracks based on the type of research:
- Journalistic — investigative pieces, primary source research, source-heavy narrative work
- Industry analysis — market research and strategy, signal detection
- Academic/Comprehensive — deep systematic research when depth matters most
All three share the same lifecycle (Scope → Gather → Evaluate → Analyze → Synthesize → Report) but differ in evidence standards, speed, and output format.
Media evidence is a technical-verification extension, not a fourth operational track. This skill owns research scope, source evaluation, claim closure, sampling-completeness audits, exclusions, and durable preservation. The ffmpeg skill owns FFmpeg commands, media probes, extraction, editing, rendering, and target verification; human or capable reviewers own semantic/editorial observations and approval. Load references/media-evidence-routing.md whenever a research conclusion depends on media tooling, sampled frames/audio/transcripts, or editorial judgment.
When not to use
Do not load this skill for:
- A single factual lookup or a quick answer — respond directly; a full research lifecycle adds cost without adding credibility.
- Direct implementation work that needs no investigation — build and verify the change instead (
backend-engineering,frontend-engineering). - Operating a specific retrieval or capture tool — load that tool's skill for runbook-level configuration and diagnostics.
- Raw capture of web content without evaluation or synthesis — the capture tool's own skill covers fetching; this skill starts where source evaluation begins.
- Structuring already-gathered findings into durable summaries, analysis files, and evidence dossiers — use
artifact-pyramidsfor the output architecture. - Persisting captured sources into durable notes across a repeated research-to-note sequence — use
research-and-vault.
The Research Lifecycle
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/media-claim-ledger.md 1.6 KB
- assets/research-brief.md 2.5 KB
- assets/research-log.md 1.7 KB
- evals/evals.json 18 KB
- README.md 2.7 KB
- references/industry-analysis.md 6.8 KB
- references/journalistic-research.md 8.4 KB
- references/media-evidence-routing.md 4.7 KB
- references/research-lifecycle.md 4.1 KB
- references/source-evaluation.md 3.6 KB
- references/source-index.md 374 B
- references/structured-analytic-techniques.md 4.3 KB
- references/synthesis-patterns.md 3.1 KB
- references/technical-verification.md 4.7 KB
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.
- 3d ago Changed · +5 lines · +19 tokens per session 8070a34a707b
- 9d ago First seen · 110 lines · 52 tokens per session scan A 3693f1a87d2f
research-methodology is a skill published in the GitHub repository magnus919/agent-skills (76 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,746 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
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…
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…