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/trends-catalog)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/trends-catalog"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/trends-catalog/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/trends-catalog"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/trends-catalog.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.00134 | $0.03352 |
| Opus 5.5 | $0.00054 | $0.01341 |
| Sonnet 5.5 | $0.00027 | $0.00670 |
| Haiku 4.5 | $0.00013 | $0.00335 |
Grade A, and why
trends-catalog 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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Industry Catalog
Context Independence
This skill reads ALL required state from pursuit project files and catalog directories — it does not depend on prior conversation context. If invoked after trends-resume or value-modeler, context compaction is safe and recommended before starting.
Before executing any operation, run /compact to free working memory. Catalog import operations read the full tips-value-model.json and merge it with existing catalog entities, which benefits from maximum available context.
If /compact is unavailable or this is the first skill in the session, skip compaction and proceed directly.
Manage persistent industry catalogs — the reusable knowledge base that makes each successive customer pursuit faster, more consistent, and more valuable.
Why Catalogs Matter
Without catalogs, every TIPS pursuit starts from scratch. The trend-scout generates candidates, the value-modeler builds paths and solutions, but all that structured knowledge lives only in the pursuit directory. The next customer engagement in the same industry repeats the same work.
Catalogs solve this by creating a persistent, curated repository per industry/subsector. When a new pursuit is initialized, it inherits relevant TIPs, Solution Templates, SPIs, and Metrics from the catalog — giving the consultant a head start and ensuring consistency across engagements.
This implements the centralized repository concept from the TIPS Value Modeler methodology (WO2018046399A1, Claim 3 and Fig. 4).
Catalog Structure
cogni-trends/catalogs/{industry}/{subsector}/
├── catalog.json # Root manifest (industry, version, stats)
├── tips-entities.json # Curated TIP entities (T, I, P roles)
├── solution-templates.json # Proven Solution Templates
├── spis.json # Validated Solution Process Improvements
├── metrics.json # Effective success KPIs
├── collaterals.json # Available supporting content
└── .history/ # Version snapshots (catalog.json copies)
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 · 366 lines · 134 tokens per session scan A e4963e892b4d
trends-catalog is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 134 tokens to every session and 3,352 once invoked, about $0.0005 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…