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-dashboard)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/trends-dashboard"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/trends-dashboard/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-dashboard"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/trends-dashboard.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.00103 | $0.03940 |
| Opus 5.5 | $0.00041 | $0.01576 |
| Sonnet 5.5 | $0.00021 | $0.00788 |
| Haiku 4.5 | $0.00010 | $0.00394 |
Grade A, and why
trends-dashboard 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TIPS Dashboard
Generate a self-contained HTML dashboard that visualizes the entire TIPS project lifecycle — from trend scouting candidates through value modeling themes to report and catalog status. The dashboard opens in the user's browser with an interactive three-panel layout inspired by knowledge-graph explorers.
Context Independence
This skill reads ALL required state from project files (trend-scout output, value model, report, catalog) — it does not depend on prior conversation context. If invoked after trends-resume or at the end of a heavy session, context compaction is safe and recommended before starting.
Before executing Step 1, run /compact to free working memory. Dashboard generation reads multiple large JSON files and produces a self-contained HTML document with embedded D3 visualizations — maximum available context ensures the full project data can be processed in one pass.
If /compact is unavailable or this is the first skill in the session, skip compaction and proceed directly.
Core Concept
TIPS projects produce rich structured data across multiple phases (trend-scout → value-modeler → trend-report → catalog). This data lives in separate JSON files and markdown outputs that are hard to reason about in aggregate. The dashboard turns all of it into a single interactive visual — navigating phases, drilling into entities, and exploring TIPS relationships (Trend → Implication → Possibility → Solution) through a force-directed graph.
It complements trends-resume (quick text-based status check) the way portfolio-dashboard complements portfolio-resume in cogni-portfolio: one is for quick re-entry, the other for visual exploration and presentation.
Information Architecture
The layout follows a three-panel design with phase-based navigation:
┌─────────────────────────────────────────────────────────────┐
│ NAVBAR: [Overview] [Scout] [Value Model] [Report] [Catalog] │
└─────────────────────────────────────────────────────────────┘
┌────────────┬──────────────────────────┬─────────────────────┐
│ LEFT │ MAIN CONTENT │ RIGHT PANEL │
│ Section │ (phase-specific) │ ┌─────────────────┐ │
│ Index │ │ │ TIPS Graph │ │
│ │ │ │ (D3 force) │ │
│ - item │ │ │ T → I → P → S │ │
│ - item │ │ ├─────────────────┤ │
│ - item │ │ │ Entity Detail │ │
│ │ │ │ (on click) │ │
│ │ │ └─────────────────┘ │
└────────────┴──────────────────────────┴─────────────────────┘
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 1d3eeacf7321
- 1mo ago Changed 3c40331f953b
- 1mo ago First seen · 256 lines · 103 tokens per session scan A 980ce9949a1c
trends-dashboard is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 103 tokens to every session and 3,940 once invoked, about $0.0004 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.