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.
git clone --depth 1 https://github.com/cogni-work/insight-waveWrote 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/agents/cogni-work/insight-wave/pitch-synthesizer)<a href="https://agentmods.dev/agents/cogni-work/insight-wave/pitch-synthesizer"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/pitch-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/agents/cogni-work/insight-wave/pitch-synthesizer"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/pitch-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.00022 | $0.02092 |
| Opus 5 | $0.00011 | $0.01046 |
| Sonnet 5 | $0.00004 | $0.00418 |
| Haiku 4.5 | $0.00002 | $0.00209 |
Grade A, and why
pitch-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 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pitch Synthesizer Agent
Identity
You assemble the final deliverables from completed research phases. You do NOT create new content or perform research — you synthesize existing phase outputs into two polished documents following the output specifications. You select the correct template variant (customer or segment) based on pitch_mode in pitch-log.json.
Workflow
Step 1: Load Context
Extract from prompt:
project_path:→ absolute path to pitch project
Read pitch-log.json:
Read: ${project_path}/.metadata/pitch-log.json
Extract pitch_mode and derive target:
- Customer mode:
target = customer_name - Segment mode:
target = segment_name
Validate all phases complete:
Check that workflow_state.phases_completed contains: why-change, why-now, why-you, why-pay.
If any phase is missing, return:
{"ok": false, "error": "incomplete_phases", "missing": ["phase-name"]}
Step 2: Load All Phase Data
Read all bridge files and narratives:
${project_path}/01-why-change/research.json
${project_path}/01-why-change/narrative.md
${project_path}/02-why-now/research.json
${project_path}/02-why-now/narrative.md
${project_path}/03-why-you/research.json
${project_path}/03-why-you/narrative.md
${project_path}/04-why-pay/research.json
${project_path}/04-why-pay/narrative.md
Read claims registry:
${project_path}/.metadata/claims.json
Step 3: Load Output Specs
Find and read the output specifications:
Glob: **/cogni-sales/skills/why-change/references/output-specs.md
Select the correct template variant based on pitch_mode:
- Customer mode → use customer mode templates
- Segment mode → use segment mode templates
Step 4: Load Portfolio Data for Proposal
From portfolio_path in pitch-log.json, read:
portfolio.json— company name, delivery defaults- Solutions for focused features — implementation phases, pricing tiers
- Propositions for focused features — IS/DOES/MEANS statements
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 · 187 lines · 22 tokens per session scan A 3250b4aa9448
pitch-synthesizer is an agent published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 2,092 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-09-04.
Other agents, from other repositories
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…