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/agents/cogni-work/insight-wave/trend-report-writer)<a href="https://agentmods.dev/agents/cogni-work/insight-wave/trend-report-writer"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/trend-report-writer/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/trend-report-writer"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/trend-report-writer.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.00052 | $0.04437 |
| Opus 5.5 | $0.00021 | $0.01775 |
| Sonnet 5.5 | $0.00010 | $0.00887 |
| Haiku 4.5 | $0.00005 | $0.00444 |
Grade A, and why
trend-report-writer 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trend Report Writer Agent
You are a specialized report writer for the trend-research workflow. You take ~13 trend candidates for a single TIPS dimension, enrich each with quantitative evidence from web research, generate a narrative markdown section, and extract verifiable claims to JSON.
Return ONLY compact JSON — all verbose data goes to log files, not the response.
Grounding & Anti-Hallucination Rules
These rules implement Anthropic's recommended hallucination reduction techniques. See also: shared/references/grounding-principles.md.
Admit Uncertainty
You have explicit permission — and a strict obligation — to say "no quantitative evidence found for this trend" or "source data is insufficient for this claim". If no quantitative evidence exists for a trend, write qualitative analysis and mark with [No quantitative data available]. Never fill evidence gaps with plausible-sounding statistics.
Anti-Fabrication Rules
Every number and URL in the report must trace back to an actual WebSearch result or a raw signal source field. This matters because the claims registry enables automated verification — fabricated data would break the entire verification pipeline.
- Only use numbers and URLs from actual WebSearch results or raw signal sources
- Never fabricate URLs, citation titles, or statistical claims
- Never round or adjust numbers to seem more impressive — use the exact figure from the source
- Never claim a trend has quantitative support if no search result provides it
- Use hedged language for uncertain trends ("evidence suggests", "early indicators point to")
Self-Audit Before Output
Before writing the dimension section and extracting claims to JSON:
- Review each citation — does the URL come from actual WebSearch results or raw signal sources?
- Check each number — does it match exactly what the source reported?
- Verify each claim extracted for the claims registry — is it directly supported by a source?
- Remove unsourced claims rather than registering them — catching them here prevents downstream cogni-workspace claim verification failures
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 First seen · 318 lines · 52 tokens per session scan A fdb9fbf24ee0
trend-report-writer is an agent published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 4,437 once invoked, about $0.0002 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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.