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/hermes-profiles --skill research-methodologygit clone --depth 1 https://github.com/magnus919/hermes-profilesWrote 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/hermes-profiles/research-methodology)<a href="https://agentmods.dev/skills/magnus919/hermes-profiles/research-methodology"><img src="https://agentmods.dev/badge/skills/magnus919/hermes-profiles/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/hermes-profiles/research-methodology"><img src="https://agentmods.dev/badge/skills/magnus919/hermes-profiles/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.00044 | $0.00624 |
| Opus 5 | $0.00022 | $0.00312 |
| Sonnet 5 | $0.00009 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00062 |
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 12d 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 — 61 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.
The Research Lifecycle
SCOPE → GATHER → EVALUATE → ANALYZE → SYNTHESIZE → REPORT
Reference Files
Tracks
| Track | Reference | When to load |
|---|---|---|
| Journalistic | references/journalistic-research.md |
You're researching an investigative piece — primary sources, interviews, documents, series management, pre-publication verification |
| Industry analysis | references/industry-analysis.md |
You're researching an industry analysis piece — signal detection, corporate evidence, competitive intelligence, case study standards |
| Academic / Comprehensive | references/research-lifecycle.md |
You're doing deep systematic research — question scoping, search strategy, inclusion/exclusion criteria |
Shared Methodology
| Reference | When to load |
|---|---|
references/source-evaluation.md |
You need to judge whether a source is credible — CRAAP test, triangulation, reliability tiers |
references/structured-analytic-techniques.md |
You need to evaluate competing explanations — ACH, driving forces, pre-mortem, indicators |
references/synthesis-patterns.md |
You need to combine findings from multiple sources into synthesized conclusions |
references/technical-verification.md |
You need to test a technical claim by reproducing it — benchmarks, API behavior, configuration |
Assets
| Asset | What it produces |
|---|---|
assets/research-brief.md |
Structured brief with findings, confidence assessment, evidence table, open questions |
assets/research-log.md |
Traceable record of searches, sources, and decisions |
What ships with it
9 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/research-brief.md 1.6 KB
- assets/research-log.md 822 B
- references/industry-analysis.md 6.8 KB
- references/journalistic-research.md 8.4 KB
- references/research-lifecycle.md 4.1 KB
- references/source-evaluation.md 3.6 KB
- references/structured-analytic-techniques.md 4.3 KB
- references/synthesis-patterns.md 3.1 KB
- references/technical-verification.md 4.2 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.
- 12d ago First seen · 61 lines · 44 tokens per session scan A 598a31744032
research-methodology is a skill published in the GitHub repository magnus919/hermes-profiles (171 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 624 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-30.
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…
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…
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…
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…