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-websiteWrote 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/website-plan)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/website-plan"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/website-plan/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/website-plan"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/website-plan.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.00129 | $0.04959 |
| Opus 5.5 | $0.00052 | $0.01984 |
| Sonnet 5.5 | $0.00026 | $0.00992 |
| Haiku 4.5 | $0.00013 | $0.00496 |
Grade A, and why
website-plan 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Website Plan
Plan the site structure by discovering available content, proposing pages, and mapping content sources to page templates. Produces website-plan.json — the blueprint that website-build executes.
Prerequisites
A website-project.json must exist (created by website-setup). If not found, redirect to the setup skill.
Workflow
1. Load Project Configuration
Read website-project.json to get:
- Content source paths (portfolio, marketing)
- Company details (name, tagline, language)
- Build options (hero renderer, blog, case studies)
- Content discovery counts
2. Deep Content Scan
Go beyond the counts from setup — read actual content to understand what's available for each page type.
Portfolio Scan
Narratives first — these are the primary spine of narrative pages (home, about, capability, persona, approach). Raw entity JSON becomes enrichment, not the spine.
The v2 portfolio-communicate customer-narrative layout produces one arc-structured file per website component. Each file carries arc_id + arc_display_name in its YAML frontmatter (see cogni-portfolio/skills/portfolio-communicate/references/templates-customer-narrative.md for the scope → arc mapping). Read the arc id once per file and store it on the plan entry — step 6a dispatches on it:
- Read
output/communicate/customer-narrative/home.md— frontmatter + prose. Arc:jtbd-portfolio. Spine for the homepage. - Read
output/communicate/customer-narrative/about.md— frontmatter + prose. Arc:company-credo. Spine for the About page (now a structured narrative page, not a flat entity page). - Read
output/communicate/customer-narrative/approach.md— frontmatter + prose. Arc:engagement-model. Spine for the How-We-Work / Unser Ansatz page. - Read every
output/communicate/customer-narrative/capabilities/*.md— each becomes the spine for one capability page. Arc:corporate-visions. Extract the feature slug from the filename. - Read every
output/communicate/customer-narrative/for/*.md— each becomes the spine for one persona landing page. Arc:jtbd-portfolio. Extractmarket+personaslugs from frontmatter (or from the{market}--{persona}filename).
What ships with it
1 file 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 83cecd66b7bf
- 1mo ago Changed c0443cfaeac6
- 1mo ago First seen · 309 lines · 129 tokens per session scan A e381ece9e776
website-plan is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 129 tokens to every session and 4,959 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…