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 hknc/claude-evolve --skill research-synthesizegit clone --depth 1 https://github.com/hknc/claude-evolveWrote 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/hknc/claude-evolve/research-synthesize)<a href="https://agentmods.dev/skills/hknc/claude-evolve/research-synthesize"><img src="https://agentmods.dev/badge/skills/hknc/claude-evolve/research-synthesize/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/hknc/claude-evolve/research-synthesize"><img src="https://agentmods.dev/badge/skills/hknc/claude-evolve/research-synthesize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00058 | $0.01158 |
| Opus 5 | $0.00029 | $0.00579 |
| Sonnet 5 | $0.00012 | $0.00232 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
research-synthesize 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 10d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Synthesize Skill
You gather information from multiple sources and synthesize into coherent understanding.
Philosophy
- Multiple sources - Don't rely on single source
- Critical evaluation - Assess credibility and recency
- Synthesis over collection - Combine into insight, not just list
- Actionable output - End with what user can do with this
Process
1. Define Research Question
Clarify what needs to be learned:
- What specific question(s)?
- What decisions will this inform?
- What depth is needed?
- Any constraints (recency, source types)?
2. Identify Source Strategy
| Research Type | Sources |
|---|---|
| Technical (how-to) | Official docs, GitHub, Stack Overflow |
| Comparison | Benchmarks, reviews, case studies |
| Current state | Recent articles, announcements, changelogs |
| Best practices | Industry guides, expert blogs, standards |
| Market/competitive | Company sites, analyst reports, news |
3. Gather in Parallel
Use Task tool to research multiple aspects simultaneously:
Spawn parallel research tasks:
Task 1: Search official documentation and guides
Task 2: Search recent articles and blog posts (last 2 years)
Task 3: Search community discussions (Reddit, HN, forums)
Task 4: Search for benchmarks or comparisons
Each task returns:
- Key findings
- Source credibility (official/community/anecdotal)
- Recency
- Relevance to question
4. Evaluate Sources
For each source, assess:
| Factor | Questions |
|---|---|
| Credibility | Who wrote it? Official source? Known expert? |
| Recency | When written? Still accurate? |
| Bias | Vendor content? Affiliate? Agenda? |
| Depth | Surface overview or deep analysis? |
| Corroboration | Do other sources agree? |
5. Synthesize Findings
Combine sources into coherent understanding:
## Research Synthesis: [Topic]
### Question
[What we set out to learn]
### Key Findings
**Consensus (multiple sources agree):**
- [Finding with high confidence]
- [Finding with high confidence]
**Likely (some evidence):**
- [Finding with medium confidence]
**Uncertain (conflicting or limited):**
- [Finding needing more research]
### Source Analysis
| Source | Type | Recency | Key Contribution |
|--------|------|---------|------------------|
| [Source 1] | Official | 2026 | [What it told us] |
| [Source 2] | Community | 2025 | [What it told us] |
### Implications
[What this means for user's decision/work]
### Gaps
[What we couldn't find / needs more research]
### Recommended Actions
[What user should do with this information]
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.
- 10d ago First seen · 203 lines · 58 tokens per session scan A 0e81af71d4c3
research-synthesize is a skill published in the GitHub repository hknc/claude-evolve (8 stars, last pushed 7mo ago), licensed MIT. It adds 58 tokens to every session and 1,158 once invoked, about $0.0003 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.
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…