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/verify-trend-report)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/verify-trend-report"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/verify-trend-report/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/verify-trend-report"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/verify-trend-report.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.00177 | $0.04695 |
| Opus 5.5 | $0.00071 | $0.01878 |
| Sonnet 5.5 | $0.00035 | $0.00939 |
| Haiku 4.5 | $0.00018 | $0.00470 |
Grade A, and why
verify-trend-report 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 — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Trend Report Skill
Quality gate for a generated trend report. Verifies every quantitative claim against its cited source via cogni-workspace:claims, runs a cross-theme structural review, applies corrections through the revisor when deviations or structural issues are found, and surfaces the downstream polish option at the end before handing back to /trends-resume for the Claude Design brief, catalog and dashboard paths. Runs in a fresh context window — separate from the trend-synthesis pipeline — so claims verification, the review loop, and revision get the full attention they deserve without competing for context with research data.
Purpose
trend-synthesis produces a draft (tips-trend-report.md) plus a claims registry (tips-trend-report-claims.json). This skill is the dedicated re-entry point that lifts that draft to a deliverable:
- Verifies claims against source URLs via
cogni-workspace:claims - Lets the user steer corrections (proceed / fix specific deviations / drop claims / accept)
- Runs
trend-report-reviewerfor cross-theme structural quality - Dispatches
trend-report-revisorto apply corrections, remove unverifiable claims, and find replacement evidence - Surfaces downstream options: executive polish (
cogni-publishing:copywriter), then hands back to/trends-resumefor the Claude Design brief, catalog and dashboard paths
Prerequisites
trend-synthesishas produced both{PROJECT_PATH}/tips-trend-report.mdand{PROJECT_PATH}/tips-trend-report-claims.jsoncogni-workspaceinstalled (recommended — graceful degradation when thecogni-workspace:claimsskill is absent: structural review only, see Error Handling)- Optional:
cogni-publishing:copywriterfor the downstream polish option; if cogni-publishing is absent, skip polish gracefully and keep the verified report
Path Variables
| Variable | Purpose | Example |
|---|---|---|
CLAUDE_PLUGIN_ROOT |
Plugin installation (skills, references) | ~/.claude/plugins/marketplaces/cogni-trends |
PROJECT_AGENTS_OPS_ROOT |
Workspace root where projects live (set by cogni-workspace) | User's workspace directory |
What ships with it
3 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.
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 · +1 lines 4b58f7374197
- 1mo ago Changed · -5 lines · -3 tokens per session 4c60fc473da7
- 1mo ago Changed c011b4684a6d
- 1mo ago First seen · 417 lines · 180 tokens per session scan A 55f0ed60fb85
verify-trend-report is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 177 tokens to every session and 4,695 once invoked, about $0.0007 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…