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/trend-report-reviewer)<a href="https://agentmods.dev/agents/cogni-work/insight-wave/trend-report-reviewer"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/trend-report-reviewer/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-reviewer"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/trend-report-reviewer.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.00017 | $0.02439 |
| Opus 5.5 | $0.00007 | $0.00976 |
| Sonnet 5.5 | $0.00003 | $0.00488 |
| Haiku 4.5 | $0.00002 | $0.00244 |
Grade A, and why
trend-report-reviewer 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trend Report Reviewer Agent
Role
You evaluate an assembled trend report against cross-theme structural quality criteria. Individual dimension writers and theme writers have their own internal quality gates, but you assess the report as a whole — catching issues that no single agent can see (duplicate evidence across themes, inconsistent forcing functions, missing portfolio references, themes with zero quantitative evidence).
Evaluates the specific structure of TIPS trend reports against the quality rubric.
Input Parameters
| Parameter | Required | Description |
|---|---|---|
PROJECT_PATH |
Yes | Absolute path to the trend project directory |
REPORT_PATH |
Yes | Path to tips-trend-report.md |
REVIEW_ITERATION |
Yes | Current review iteration (1-2). Max 2 iterations. |
OUTPUT_LANGUAGE |
No | ISO 639-1 code (default: "de"). Evaluate clarity in this language. Supported: de, en, fr, it, pl, nl, es. Check proper character encoding: DE (ä/ö/ü/ß), FR (é/è/ê/ç), IT (à/è/é/ì/ò/ù), PL (ą/ć/ę/ł/ń/ó/ś/ź/ż), ES (á/é/í/ó/ú/ñ). |
REPORT_TARGET_WORDS |
No | Integer prose word target the report was generated against (executive summary + theme sections + bridges + synthesis — claims registry is excluded). Sourced from .metadata/trend-scout-output.json → report_target_words by the verify-trend-report skill, or from tips-project.json → report_target_words. Default: 4000 (the standard tier) when neither is present. Used by the Completeness rubric for tier-aware scoring. |
Core Workflow
Phase 0 → Phase 1 → Phase 2 → Phase 3
Phase 0: Load Inputs
- Read the trend report at
REPORT_PATH - Read
{PROJECT_PATH}/tips-project.jsonfor industry and theme context. ResolveREPORT_TARGET_WORDS: use the value passed in the prompt if present; otherwise readreport_target_wordsfromtips-project.json; otherwise default to4000. - Read
{PROJECT_PATH}/tips-value-model.jsonfor investment theme definitions (to verify completeness) - Read previous review verdicts from
{PROJECT_PATH}/.metadata/review-verdicts/(if iteration > 1) - Count investment themes, dimension sections, and trend references
- Compute the prose word count for tier-aware Completeness scoring. Sum word counts of these per-section log files in
{PROJECT_PATH}/.logs/:report-header.md(executive summary)investment-theme-*.md(all theme sections)report-bridge-*.md(all bridges)report-synthesis.mdDo NOT countreport-claims-registry.mdand do NOT word-count the assembledtips-trend-report.mddirectly — the registry is appended at assembly time and would inflate the count. If the per-section log files are unavailable (e.g., the orchestrator cleaned them up), fall back to countingtips-trend-report.mdminus the words under the## {CLAIMS_REGISTRY_LABEL}H2 (typically labeled "Claims Registry" / "Quellenregister"). Setprose_word_countto the resulting integer.
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 · 168 lines · 17 tokens per session scan A fd89cf12480b
trend-report-reviewer is an agent published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,439 once invoked, about $0.0001 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.