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-resume)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/trends-resume"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/trends-resume/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-resume"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/trends-resume.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.00136 | $0.04113 |
| Opus 5.5 | $0.00054 | $0.01645 |
| Sonnet 5.5 | $0.00027 | $0.00823 |
| Haiku 4.5 | $0.00014 | $0.00411 |
Grade A, and why
trends-resume 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TIPS Resume
Session entry point for returning to trend scouting work. This skill orients the user by showing where they left off and what to do next — the dashboard view that keeps multi-session TIPS projects on track.
Core Concept
TIPS projects span multiple sessions and skills (trend-scout → value-modeler → trend-research → trend-synthesis [± trend-booklet] → verify-trend-report). Without a clear re-entry point, users lose context between sessions and waste time figuring out what they already did. This skill bridges that gap: it reads the project state, surfaces progress at a glance, and recommends the most valuable next step.
Workflow
Plugin root resolution. Every bash call below resolves the plugin root inline as ${CLAUDE_PLUGIN_ROOT:-$(ls -td "$HOME"/.claude/plugins/cache/insight-wave/cogni-trends/*/ | head -1)}. When Claude Code injects $CLAUDE_PLUGIN_ROOT (the normal case) the fallback never runs. If the harness fails to inject it (observed in some sessions, where bash $CLAUDE_PLUGIN_ROOT/... would produce No such file or directory), the inline fallback discovers the most recently cached plugin root automatically — no failed first call, no recovery prompt. Keep the inline form in every call; do not strip it.
1. Find TIPS Projects
Discover TIPS projects in the workspace using the discovery script.
Determine the workspace root before calling the script. The workspace root is the directory that contains the cogni-trends/ project folder. Check in this order:
$PROJECT_AGENTS_OPS_ROOT— if set (viasettings.local.jsonenv block), use it- Otherwise, look for a
cogni-trends/directory under the current working directory - If not found under
$PWD, check if there's a.workspace-config.jsonnearby that indicates the workspace location
Pass the root explicitly with --root:
bash "${CLAUDE_PLUGIN_ROOT:-$(ls -td "$HOME"/.claude/plugins/cache/insight-wave/cogni-trends/*/ | head -1)}/scripts/discover-projects.sh" --json --root "<workspace-root>"
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 5b6c61e8f02e
- 1mo ago Changed · -1 lines b0fa46e87f17
- 1mo ago Changed · -2 lines f1f1636272c0
- 1mo ago First seen · 241 lines · 136 tokens per session scan A 7c3c1539aa42
trends-resume is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 136 tokens to every session and 4,113 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
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.