Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add cogni-work/insight-wave/plugin install cogni-trendsWrote 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/cogni-work/insight-wave/trend-synthesis)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/trend-synthesis"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/trend-synthesis/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/cogni-work/insight-wave/trend-synthesis"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/trend-synthesis.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.00237 | $0.08450 |
| Opus 5.5 | $0.00095 | $0.03380 |
| Sonnet 5.5 | $0.00047 | $0.01690 |
| Haiku 4.5 | $0.00024 | $0.00845 |
Grade A, and why
trend-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 1mo 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 — 573 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trend Synthesis
Compose the canonical TIPS trend report from /trend-research output. The report's H2 spine is the 4 Smarter Service dimensions (T → I → P → S); investment themes nest under their anchor dimension as H3 theme-cases (Stake / Move / Cost-of-Inaction). Closes on a Foundations-anchored "Capability Imperative" synthesis. The four dimensions are not parallel essays — they trace a single rising-tension arc. The Storytelling Spine section below is the load-bearing reference for that arc.
Purpose
Transform the research manifest plus enriched per-trend evidence into a CxO-grade strategic report:
- Locate the research output (gate on manifest existing; warn on drift)
- Propose a punchy report title (subtitle = research topic)
- Pick a length tier and compute per-section word budgets (smarter-service formula only)
- Anchor each investment theme to its dominant TIPS dimension
- Write the shared dimension primer (orchestrator)
- Dispatch N parallel theme-case writers — each writes a micro-story (Storytelling Spine)
- Dispatch 4 sequential dimension composers (T → I → P → S, voice consistency, with bridge sentences)
- Compose the executive summary — opens on the Why-Now hook
- Build the claims registry with a dimension column
- Write the "Capability Imperative" synthesis section — closes with a callback to the Why-Now hook
- Assemble + merge claims →
tips-trend-report.md+tips-trend-report-claims.json - Update finalization metadata; auto-recommend
/verify-trend-report
Evidence lives in research outputs; this skill never re-runs WebSearch.
Language Support
Full German and English support. This skill follows the shared language resolution pattern — see $CLAUDE_PLUGIN_ROOT/references/language-resolution.md.
The report inherits language from the research manifest (set during /trend-research Phase 0). The user may override at the title-proposal step (Step 0.5) but the new value also propagates to the manifest mirror in finalization metadata.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 11 KB
- references/capability-imperative.md 4.7 KB
- references/claims-registry-format.md 5.2 KB
- references/i18n/labels-de.md 5.2 KB
- references/i18n/labels-en.md 5.0 KB
- references/report-length-tiers.md 9.9 KB
- references/report-structure.md 1.9 KB
- references/story-arc-loop.md 7.0 KB
- references/synthesis-skeleton.md 24 KB
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.
- 1mo ago Changed a0c1ce191605
- 1mo ago Changed 15ffc2fde80a
- 1mo ago Changed · +1 lines 08f8ec58005a
- 1mo ago Changed 91d4babd07b6
- 1mo ago First seen · 572 lines · 237 tokens per session scan A 3590b28ed419
trend-synthesis is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 237 tokens to every session and 8,450 once invoked, about $0.0009 per session on Opus 5.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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…