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/qte77/claude-code-plugins/synthesizing-researchnpx skills add qte77/claude-code-plugins --skill synthesizing-researchgit clone --depth 1 https://github.com/qte77/claude-code-pluginsWrote 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/qte77/claude-code-plugins/synthesizing-research)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/synthesizing-research"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/synthesizing-research.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 | $0.00041 | $0.00832 |
| Opus 5 | $0.00020 | $0.00416 |
| Sonnet 5 | $0.00008 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
synthesizing-research 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 3d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synthesizing Research (Phase 5)
Target: $ARGUMENTS
Phase 5 of the GTM pipeline. Depends on all prior phases (0-4). Produces a unified GTM narrative integrating technical, market, and strategic findings. This output drives Phase 6 slide deck generation.
Mode Awareness
Read config/mode.md before starting:
concise— Executive summary (1 page), key findings table, single recommended pathdetailed— Full integrated narrative, alternative scenarios, confidence annotationsconservative— Lead with validated evidence; clearly separate confirmed from inferredambitious— Lead with opportunity thesis; build the bull case narrative
Inputs
results/phase-0/capability-profile.mdresults/phase-1a/competitor-map.mdresults/phase-1b/market-analysis.mdresults/phase-2/pmf-assessment.mdresults/phase-3/gtm-strategy.mdresults/phase-4/contradiction-analysis.mdconfig/comments_gtm.md— GTM preferences for framingconfig/mode.md— Style and approach settings
Workflow
- Read all prior phase outputs including contradiction resolutions from Phase 4
- Construct the narrative arc: Source capability → Market opportunity → PMF evidence → GTM path
- Resolve outstanding contradictions from Phase 4 into final recommendations
- Assign confidence ratings to all major claims (High/Medium/Low)
- Identify the single recommended GTM path and articulate why
- Document alternatives with tradeoffs for decision-maker context
- Validate against criteria — Check
config/validation_criteria.mdPhase 5 gates
Output
Write to results/phase-5/:
synthesis.md
# GTM Research Synthesis
## Executive Summary
[3-5 sentence narrative: what we found, what it means, what we recommend]
## Key Findings by Phase
| Phase | Key Finding | Confidence |
|-------|-------------|------------|
| 0 — Source | [finding] | High/Medium/Low |
| 1A — Landscape | [finding] | High/Medium/Low |
| 1B — Market | [finding] | High/Medium/Low |
| 2 — PMF | [finding] | High/Medium/Low |
| 3 — GTM | [finding] | High/Medium/Low |
| 4 — Gaps | [finding] | High/Medium/Low |
## Integrated GTM Narrative
### The Opportunity
[Market context and timing rationale]
### The Fit
[How product capabilities match market needs]
### The Path
[Recommended GTM motion and why]
## Recommended GTM Path
[Specific, actionable recommendation with first 3 steps]
## Alternative Paths
### Alternative 1: [Name]
- Tradeoff: [upside vs downside]
## Confidence Assessment
- Claims with High confidence: [N]
- Claims with Medium confidence: [N]
- Claims with Low confidence: [N] — [action needed]
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.
- 3d ago First seen · 101 lines · 41 tokens per session scan A 26e3802d20a2
synthesizing-research is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 41 tokens to every session and 832 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
orchestrator
FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.
flutter-guide
Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.
maestro-flutter
Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.
android-kotlin-compose
Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…
android-kotlin-coroutines
Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…
codex-advisor
Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…