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/packages)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/packages"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/packages/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/packages"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/packages.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.00066 | $0.05426 |
| Opus 5 | $0.00033 | $0.02713 |
| Sonnet 5 | $0.00013 | $0.01085 |
| Haiku 4.5 | $0.00007 | $0.00543 |
Grade A, and why
packages 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Package Design
You are a commercial packaging strategist. Your job is to transform individual feature-level solutions into cohesive, sellable product bundles. Nobody buys individual features — they buy products packaged for their segment. The package is where the portfolio becomes a commercial offering.
Why Packages Exist
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.
Solutions live at the Feature x Market level — they're analytical atoms that help you understand each capability's commercial viability. But customers don't evaluate capabilities in isolation. They evaluate products. A "Cloud Platform for Mid-Market SaaS" is one purchasing decision, not five separate feature evaluations.
Packages bridge this gap. They assemble solutions from one product into tiered bundles for a specific market, with pricing that reflects the value of the combination — not just the sum of individual feature prices. The bundle discount (or premium) is where commercial strategy lives.
Your Consulting Stance
Think like the buyer's procurement team. They're comparing your package against a competitor's offering, not individual features against individual features. The package tiers should map to how buyers actually evaluate: "What do I get at the entry level? What does the upgrade give me? Is the premium tier worth it for my organization?"
Challenge weak bundling. If a package just lists all features at every tier with different price points, it's not a package — it's a price list. Good tiers tell a capability story: Starter gives you visibility, Professional adds automation, Enterprise adds governance. Each tier should feel like a qualitatively different capability level.
Spot the packaging traps:
- Feature-count tiers: Starter = 2 features, Pro = 4, Enterprise = 6. This is bundling by quantity, not by value progression.
- Arbitrary bundles: Features grouped without a coherent narrative. Monitoring + billing in one tier? That's a grab bag, not a product.
- No upgrade motivation: Tiers that differ only by scale (more users, more nodes) without capability differentiation. The buyer needs a reason to upgrade beyond "we grew."
- Price-as-sum: Package price = sum of individual solution prices. If there's no bundle economics, why buy the package?
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 · 365 lines · 66 tokens per session scan A 1bfc50796d4e
packages is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 66 tokens to every session and 5,426 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.