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/portfolio-canvas)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/portfolio-canvas"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/portfolio-canvas/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/portfolio-canvas"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/portfolio-canvas.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.00103 | $0.03903 |
| Opus 5 | $0.00051 | $0.01951 |
| Sonnet 5 | $0.00021 | $0.00781 |
| Haiku 4.5 | $0.00010 | $0.00390 |
Grade A, and why
portfolio-canvas 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Canvas-to-Portfolio Bootstrap
Seed a cogni-portfolio project from a Lean Canvas (or Business Model Canvas). This skill bridges the gap between a founding-stage hypothesis document and the structured entity model that the rest of the portfolio pipeline expects.
Why This Exists
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.
A lean canvas is a hypothesis document — it captures what you think the business is. The portfolio pipeline is a messaging system — it captures what you sell. For a founding-stage company these are the same thing, but the data shapes are different. This skill does the translation so that downstream skills (propositions, solutions, packages, export) work without modification.
The key insight: a canvas already contains products, markets, and pricing buried in its sections — they just need to be extracted, properly typed, and marked as early-stage (maturity: "concept", readiness: "planned", priority: "beachhead").
Prerequisites
- A lean canvas file (markdown, typically with numbered sections: Problem, Customer Segments, UVP, Solution, Channels, Revenue Streams, Cost Structure, Key Metrics, Unfair Advantage)
- No existing portfolio project required — this skill can create one via
portfolio-setupif needed, or enrich an existing project
Canvas Section → Portfolio Entity Mapping
| Canvas Section | Portfolio Entity | How It Maps |
|---|---|---|
| Customer Segments | Markets | Each segment becomes a market. Primary → priority: "beachhead", Secondary → "expansion", Tertiary → "aspirational". Pain points feed downstream proposition DOES/MEANS. |
| Solution (layers/components) | Products | Each distinct solution layer or component becomes a product with maturity: "concept" and inferred revenue_model. |
| Solution (capabilities within layers) | Features | Specific capabilities mentioned within solution layers become features with readiness: "planned". |
| Solution (decided offerings) | Solution candidates | Each already-decided offering in the Solutions block is pre-registered as a marked candidate in research/solution-candidates.json (Step 6.5), so the solutions skill starts from the decided structure instead of generating 1:1 from propositions. Candidates carry status: "candidate" and live outside solutions/, so they are never counted as finished solutions. |
| Revenue Streams | Solution pricing templates | Pricing assumptions seed solution pricing or subscription fields. The revenue type (license, subscription, consulting, maintenance) determines solution_type. |
| Problem | Context | Pain points inform proposition DOES statements downstream — stored as canvas_context.problems in portfolio.json for reference. |
| UVP | Context | The overarching value proposition informs product positioning — stored as canvas_context.uvp in portfolio.json. |
| Channels | Context | Distribution channels are not portfolio entities but inform market descriptions — stored as canvas_context.channels in portfolio.json. |
| Cost Structure | Context | Cost categories inform solution cost_model downstream — stored as canvas_context.cost_structure in portfolio.json. |
| Key Metrics | Context | Stored as canvas_context.key_metrics in portfolio.json for reference. |
| Unfair Advantage | Context | Feeds differentiators in portfolio-context export — stored as canvas_context.unfair_advantage in portfolio.json. |
| Assumptions to Validate | Context | Stored as canvas_context.assumptions in portfolio.json. Referenced during proposition and solution creation so hypotheses stay visible. |
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 · 271 lines · 103 tokens per session scan A cf0786eb0edc
portfolio-canvas is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 103 tokens to every session and 3,903 once invoked, about $0.0005 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.