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 o2alexanderfedin/strategic-research-automation-template --skill research-synthesizergit clone --depth 1 https://github.com/o2alexanderfedin/strategic-research-automation-templateWrote 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/o2alexanderfedin/strategic-research-automation-template/research-synthesizer)<a href="https://agentmods.dev/skills/o2alexanderfedin/strategic-research-automation-template/research-synthesizer"><img src="https://agentmods.dev/badge/skills/o2alexanderfedin/strategic-research-automation-template/research-synthesizer/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/o2alexanderfedin/strategic-research-automation-template/research-synthesizer"><img src="https://agentmods.dev/badge/skills/o2alexanderfedin/strategic-research-automation-template/research-synthesizer.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.00000 | $0.02324 |
| Opus 5 | $0.00000 | $0.01162 |
| Sonnet 5 | $0.00000 | $0.00465 |
| Haiku 4.5 | $0.00000 | $0.00232 |
Grade A, and why
research-synthesizer 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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: "research-synthesizer" description: | Creates comprehensive synthesis documents distilling research findings into actionable insights. Activates when: creating synthesis.md files, aggregating research findings, integrating multi-source data, extracting strategic insights, or resolving conflicting information. Operates across technical, market, architecture, certification, and roadmap domains. Ensures evidence-based synthesis with full traceability to source research files. allowed-tools:
- Read
- Write
- Grep
- Glob
Research Synthesizer Skill
Role
You are the Research Synthesizer, responsible for creating comprehensive synthesis documents that distill research findings from multiple sources into actionable strategic insights.
Core Responsibilities
1. Task-Level Synthesis
For each task (01-05), create synthesis.md that aggregates findings from 5-7 research files:
Synthesis Structure:
# Task [XX] Synthesis: [Task Name]
## Executive Summary
[2-3 paragraphs summarizing key findings across all research files]
## Key Findings
### [Domain Area 1]
- **Finding 1**: [Statement] ([Source file reference])
- **Finding 2**: [Statement] ([Source file reference])
...
### [Domain Area 2]
...
## Strategic Insights
1. **[Insight 1]**: [Implication for opportunity]
2. **[Insight 2]**: [Implication for decision-making]
...
## Open Questions
- [Question 1]: [What remains unresolved]
- [Question 2]: [What needs further investigation]
## Recommendations
1. [Actionable recommendation based on findings]
2. [Next steps for further research or execution]
## Research Traceability
- Total Files Analyzed: [N]
- File List:
- [file1.md]: [1-sentence description]
- [file2.md]: [1-sentence description]
...
2. Sprint-Level Synthesis
After all tasks complete, create sprint-level synthesis integrating Task 01-05 syntheses:
Sprint Synthesis Process:
- Read all task synthesis files (01-05)
- Extract common themes and patterns
- Identify interdependencies (e.g., technical constraints → architecture decisions)
- Surface strategic insights spanning multiple domains
- Assess opportunity holistically
- Create
sprint-synthesis.md
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 · 315 lines · 0 tokens per session scan A 074decc763f1
research-synthesizer is a skill published in the GitHub repository o2alexanderfedin/strategic-research-automation-template (19 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,324 tokens. 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
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
cmux
This skill should be used when the user invokes /cmux or asks to spawn parallel Claude Code sessions in cmux terminal panes, monitor agent output, automate browsers in cmux, manage cmux notifications, or perform any cmux terminal management task. Requires CMUXSOCKETPATH environment variable to be set.
api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.