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 agentmods add skills/hyunjunjeon/deepagent-research-context-engineering/data-synthesisnpx skills add HyunjunJeon/Deepagent-research-context-engineering --skill data-synthesisgit clone --depth 1 https://github.com/HyunjunJeon/Deepagent-research-context-engineeringWrote 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/hyunjunjeon/deepagent-research-context-engineering/data-synthesis)<a href="https://agentmods.dev/skills/hyunjunjeon/deepagent-research-context-engineering/data-synthesis"><img src="https://agentmods.dev/badge/skills/hyunjunjeon/deepagent-research-context-engineering/data-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.00028 | $0.02572 |
| Opus 5 | $0.00014 | $0.01286 |
| Sonnet 5 | $0.00006 | $0.00514 |
| Haiku 4.5 | $0.00003 | $0.00257 |
Grade A, and why
data-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 6d 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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Synthesis Skill
This skill provides a structured approach to combining research findings from multiple sources into unified, coherent insights. It ensures that synthesized outputs maintain accuracy, proper attribution, and analytical depth.
When to Use This Skill
Activate this skill in the following scenarios:
Primary Use Cases
- Multi-source integration: Combining findings from 2+ research sub-agents working on related topics
- Cross-thread synthesis: Merging parallel research threads into a unified narrative
- Comparative analysis: Analyzing similarities and differences across multiple data sources
- Executive summaries: Condensing extensive research into actionable insights
- Gap identification: Finding missing information by comparing what different sources cover
Trigger Conditions
- You have gathered research from multiple sub-agents or tools
- Sources contain overlapping but not identical information
- The user needs a cohesive understanding rather than fragmented data points
- Contradictory information needs to be reconciled
- Multiple perspectives on a topic need to be unified
Synthesis Workflow
Follow this step-by-step process for effective data synthesis:
Step 1: Gather All Source Materials
Before beginning synthesis, ensure you have:
-
Inventory all sources
- List every research output, file, or response to be synthesized
- Note the origin (sub-agent ID, tool used, timestamp)
- Record the scope and focus of each source
-
Assess source quality
- Evaluate reliability (primary vs secondary sources)
- Check recency and relevance
- Identify potential biases or limitations
-
Organize by category
/research_workspace/synthesis/ ├── sources/ │ ├── agent_1_findings.md │ ├── agent_2_findings.md │ └── agent_3_findings.md ├── working/ │ └── theme_analysis.md └── output/ └── synthesized_report.md
Step 2: Identify Common Themes and Contradictions
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.
- 6d ago First seen · 377 lines · 28 tokens per session scan A 30a6b08be089
data-synthesis is a skill published in the GitHub repository HyunjunJeon/Deepagent-research-context-engineering (53 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 2,572 once invoked, about $0.0001 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
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.