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 DojoGenesis/mcp --skill research-synthesisgit clone --depth 1 https://github.com/DojoGenesis/mcpWrote 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/dojogenesis/mcp/research-synthesis)<a href="https://agentmods.dev/skills/dojogenesis/mcp/research-synthesis"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/research-synthesis.svg" alt="Measured on agentmods" 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.00039 | $0.02470 |
| Opus 5 | $0.00019 | $0.01235 |
| Sonnet 5 | $0.00008 | $0.00494 |
| Haiku 4.5 | $0.00004 | $0.00247 |
Grade A, and why
research-synthesis 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 7d 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Synthesis Skill
Version: 1.1 Author: Tres Pies Design Purpose: Turn raw research into coherent understanding — identify patterns, contradictions, and actionable insights across multiple sources.
I. Philosophy: From Information to Insight
Synthesis is insight generation, not information gathering. By systematically cataloging, cross-referencing, and synthesizing multiple sources, it uncovers patterns and contradictions that are not visible from any single source, leading to deeper, more actionable understanding.
Synthesis complements the other research modes:
- Deep Research finds answers (focused, 5 phases)
- Wide Research finds questions (broad, 4 phases)
- Research Synthesis finds patterns across sources (multi-file, 5 phases)
Deep and wide research feed into synthesis. When you have 3+ research files on a topic, synthesis extracts what no single source can reveal.
II. When to Use This Skill
- When you have 3 or more research files on a single topic
- When you need to create a literature review or competitive analysis
- When you want to consolidate notes from multiple meetings or interviews
- When
/plan-from-files(specification-driven-development plugin) routes 3+ research files here - After completing deep or wide research that produced multiple source documents
III. The 5-Step Synthesis Workflow
Step 1: Ingest & Catalog
Read all uploaded files. For each:
- Extract metadata — author, date, key topics
- Summarize key content — what does this file contribute?
- Identify type — paper, article, notes, transcript, report
- Create internal catalog listing all sources
Output: Source catalog table
### Source Catalog
| # | File | Type | Author | Date | Key Topics | Summary |
|---|------|------|--------|------|------------|---------|
| 1 | [filename] | [type] | [author] | [date] | [topics] | [one sentence] |
Step 2: Cross-Reference & Find Patterns
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.
- 7d ago First seen · 265 lines · 39 tokens per session scan A 20a3a89476f8
research-synthesis is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 2,470 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-31.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.
build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
code-formatter
Apply repository-standard formatting to minimize diff noise and meet linter expectations.