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.
npx skills add cogni-work/insight-wave --skill trends-bridgegit 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/skills/cogni-work/insight-wave/trends-bridge)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/trends-bridge"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/trends-bridge/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-bridge"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/trends-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00141 | $0.07639 |
| Opus 5 | $0.00071 | $0.03819 |
| Sonnet 5 | $0.00028 | $0.01528 |
| Haiku 4.5 | $0.00014 | $0.00764 |
Grade A, and why
trends-bridge 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 6d 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 — 720 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TIPS-Portfolio Bridge
Bidirectional flow between cogni-trends trend analysis and cogni-portfolio product messaging. This is the operational link between the "Value/Sales" side (TIPS) and the "Services/Best Practices" side (Portfolio) — connecting trend-driven insights to concrete product positioning and go-to-market.
Why This Matters
Without the bridge, TIPS and Portfolio are two separate worlds:
- TIPS identifies what matters (trends, implications, ranked solutions) but doesn't touch products.
- Portfolio structures what you sell (features, propositions, pricing) but doesn't know why it matters.
The bridge connects them: trends inform which features to prioritize, ranked solutions become new features or enrich existing ones, and portfolio constraints guide solution generation.
Prerequisites & Validation
Every bridge operation runs a pre-flight check before doing any work. The goal is to catch data gaps and industry mismatches early — before wasting time on an export or import that will produce poor results.
The pre-flight has two parts: a shared check (project discovery + industry alignment) that runs for every operation, and operation-specific validation gates (hard gates block, soft warnings continue). Industry alignment uses a 4-tier heuristic (exact / vertical / broad / none) so cross-industry intent can still be confirmed explicitly when needed.
See references/validation-gates.md for the full heuristic and gate lists.
Operations
status — Check Bridge Readiness
/bridge status
Quick readiness check without running any operations. Use this to see whether your data is ready before committing to a full bridge run.
Step 1: Discover & Validate
Run the shared pre-flight (project discovery + industry alignment). Report results but do not block on warnings — status is purely informational.
Step 2: Portfolio Readiness
Count portfolio entities and report:
Portfolio: {slug}
Products: {N} ✓ (or ✗ if 0)
Features: {N} ✓ (or ✗ if 0)
Propositions: {N} ✓ (or — if 0)
Markets: {N} ✓ (or — if 0)
Solutions: {N} (info only)
What ships with it
29 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 3.9 KB
- evals/fixtures/README.md 1.9 KB
- evals/fixtures/status-ready/portfolio/features/cloud-monitoring.json 263 B
- evals/fixtures/status-ready/portfolio/markets/mid-market-saas-dach.json 218 B
- evals/fixtures/status-ready/portfolio/portfolio.json 152 B
- evals/fixtures/status-ready/portfolio/products/cloud-platform.json 181 B
- evals/fixtures/status-ready/portfolio/propositions/cloud-monitoring--mid-market-saas-dach.json 340 B
- evals/fixtures/status-ready/tips/portfolio-context.json 244 B
- evals/fixtures/status-ready/tips/tips-project.json 176 B
- evals/fixtures/status-ready/tips/tips-value-model.json 469 B
- evals/fixtures/with-customers/portfolio/customers/mid-market-saas-dach.json 671 B
- evals/fixtures/with-customers/portfolio/features/cloud-monitoring.json 263 B
- evals/fixtures/with-customers/portfolio/markets/mid-market-saas-dach.json 218 B
- evals/fixtures/with-customers/portfolio/portfolio.json 154 B
- evals/fixtures/with-customers/portfolio/products/cloud-platform.json 181 B
- evals/fixtures/with-customers/portfolio/propositions/cloud-monitoring--mid-market-saas-dach.json 340 B
- evals/fixtures/with-customers/tips/tips-project.json 176 B
- evals/fixtures/with-customers/tips/tips-value-model.json 469 B
- evals/fixtures/without-customers/portfolio/features/cloud-monitoring.json 263 B
- evals/fixtures/without-customers/portfolio/markets/mid-market-saas-dach.json 218 B
- evals/fixtures/without-customers/portfolio/portfolio.json 157 B
- evals/fixtures/without-customers/portfolio/products/cloud-platform.json 181 B
- evals/fixtures/without-customers/portfolio/propositions/cloud-monitoring--mid-market-saas-dach.json 340 B
- evals/fixtures/without-customers/tips/tips-project.json 176 B
- evals/fixtures/without-customers/tips/tips-value-model.json 469 B
- references/opportunity-pipeline.md 6.1 KB
- references/opportunity-schema.md 8.5 KB
- references/portfolio-context-schema.md 8.3 KB
- references/validation-gates.md 5.5 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.
- 6d ago First seen · 720 lines · 141 tokens per session scan A ac85aeccb62f
trends-bridge is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 141 tokens to every session and 7,639 once invoked, about $0.0007 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…