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 agentmods add skills/cogni-work/insight-wave/why-changenpx skills add cogni-work/insight-wave --skill why-changegit 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/why-change)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/why-change"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/why-change.svg" alt="Measured on agentmods" 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.00166 | $0.04136 |
| Opus 5 | $0.00083 | $0.02068 |
| Sonnet 5 | $0.00033 | $0.00827 |
| Haiku 4.5 | $0.00017 | $0.00414 |
Grade A, and why
why-change 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 yesterday.
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 — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Why Change Pitch
Create a "Why Change" sales pitch using the Corporate Visions methodology. Supports two modes:
- Customer mode — Deal-specific pitch for a named customer. Company-specific web research, personalized framing.
- Segment mode — Reusable pitch for a market segment. Industry-level web research, generic framing that works for any organization in the segment.
Both modes produce two deliverables: sales-presentation.md (narrative arc) and sales-proposal.md (formal proposal with pricing).
Prerequisites
- At least one cogni-portfolio project with products, features, propositions, and solutions
- Customer mode: a named customer to pitch to (company name + industry)
- Segment mode: a market segment from the portfolio (e.g., "Enterprise Manufacturing DACH")
- Optional: cogni-trends project with value-modeler completed (enriches with trend evidence)
Arc Methodology
This skill applies the Corporate Visions story arc defined by the cogni-workspace narrative skill:
cogni-workspace/skills/narrative/references/story-arc/corporate-visions/arc-definition.md
The arc has four elements, each with detailed patterns the researcher agent reads and applies:
- Why Change — Disrupt status quo with unconsidered needs (problem-solution-benefit structure)
- Why Now — Create urgency with forcing functions and cost of inaction
- Why You — Differentiate with IS/DOES/MEANS (solution → outcomes → moat)
- Why Pay — Build business case with compound cost calculation
Workflow
Phase 0: Setup
Step 0.1: Portfolio Discovery
Run the discovery script to find available portfolios:
"${CLAUDE_PLUGIN_ROOT}/scripts/discover-portfolio.sh" --workspace "$(pwd)"
Present discovered portfolios to the user:
Portfolio projects found:
1. acme-cloud (4 products, 12 features, 3 markets, 8 propositions)
If only one portfolio: confirm automatically. If multiple: ask user to select.
Step 0.2: Pitch Mode & Target
Ask the user via AskUserQuestion:
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.
- yesterday First seen · 459 lines · 166 tokens per session scan A 30a2d544139c
why-change is a skill published in the GitHub repository cogni-work/insight-wave (12 stars, last pushed today), licensed Apache-2.0. It adds 166 tokens to every session and 4,136 once invoked, about $0.0008 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…