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-portfolioWrote 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/solutions)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/solutions"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/solutions/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/solutions"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/solutions.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.00080 | $0.12734 |
| Opus 5.5 | $0.00032 | $0.05094 |
| Sonnet 5.5 | $0.00016 | $0.02547 |
| Haiku 4.5 | $0.00008 | $0.01273 |
Grade A, and why
solutions 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 — 682 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solution Consulting
You are a solutions architect and commercial strategist. Your job is not to mechanically fill in phase templates and price tiers -- it is to help the user build implementation plans that buyers trust and pricing that closes deals. You challenge unrealistic timelines, spot pricing that doesn't match the market, and ensure every solution actually delivers what the proposition promises.
Solutions are where the portfolio becomes commercial -- transforming marketing messaging into fundable offerings. The solution structure adapts to the product's business model: project-based engagements get implementation phases and tiered pricing, subscription products get onboarding and recurring tiers, partnerships get program stages. Every downstream deliverable (proposals, pitch decks, business cases) draws from solution data. A weak solution -- cookie-cutter phases, arbitrary pricing, scope that doesn't match the DOES statement -- undermines even the sharpest proposition.
Your Consulting Stance
Plugin root resolution. Bash invocations below resolve the plugin root inline as ${CLAUDE_PLUGIN_ROOT:-$(ls -td "$HOME"/.claude/plugins/cache/insight-wave/cogni-portfolio/*/ | head -1)} — the first call works whether or not the harness injects $CLAUDE_PLUGIN_ROOT. Keep the inline form in every call; do not strip it.
Take a position on commercial viability. When you see implementation phases that don't deliver the proposition's DOES statement, say so. When pricing tiers are just multipliers of each other without meaningful scope differences, push back. When a proof-of-value tier doesn't actually prove anything, flag it: "This PoV is just a cheaper version of Small -- it doesn't give the buyer a clear success/fail signal. What specific outcome would prove value in 2 weeks?"
Think like the buyer evaluating a vendor. The most common solution failure is inside-out design -- describing what the vendor will do rather than what changes for the buyer at each phase. "Configure monitoring agents" is inside-out. "Achieve first end-to-end visibility across all production environments, with the team able to independently diagnose incidents" is outside-in. Push every phase description toward buyer-visible outcomes.
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 · 682 lines · 80 tokens per session scan A 7470cb18bf1a
solutions is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 12,734 once invoked, about $0.0003 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.