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-taxonomy)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/portfolio-taxonomy"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/portfolio-taxonomy/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-taxonomy"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/portfolio-taxonomy.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.00195 | $0.03931 |
| Opus 5 | $0.00097 | $0.01965 |
| Sonnet 5 | $0.00039 | $0.00786 |
| Haiku 4.5 | $0.00019 | $0.00393 |
Grade A, and why
portfolio-taxonomy 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portfolio Taxonomy
Core Concept
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.
cogni-portfolio ships 8 industry taxonomy templates — b2b-ict, b2b-saas, b2b-fintech, b2b-healthtech, b2b-martech, b2b-industrial-tech, b2b-professional-services, b2b-opensource. Each one is a 7-file bundle that drives portfolio-scan (search patterns, category tables) and maps discovered offerings to products and features via the product-template contract.
A taxonomy works best when it matches the industry you are scanning. Often the bundled 8 are close enough; sometimes they are not. This skill is how the user takes ownership of the taxonomy — clones a bundled one to edit, authors a new one, imports one from an external reference model, or maintains an existing project-local taxonomy through inspect, edit, validate, and export operations. The customized taxonomy lives inside the portfolio project at {PROJECT_PATH}/taxonomy/ — it is not shared across projects (unless explicitly exported), it is not written back to the plugin, and it survives plugin updates because it is part of the project's own data.
Resolver precedence (used by cogni-portfolio:portfolio-scan Phase 0 and cogni-portfolio:portfolio-setup Step 5):
- If
{PROJECT_PATH}/taxonomy/exists → use it (project-local wins) - Else if
portfolio.jsonhastaxonomy.type→ load$CLAUDE_PLUGIN_ROOT/templates/{type}/ - Else run the industry-match fallback against bundled templates
Project-local ownership means the user can safely edit {PROJECT_PATH}/taxonomy/template.md, categories.json, search-patterns.md, and the rest without worrying about plugin updates reverting their changes.
When NOT to use
Do not edit the bundled templates under $CLAUDE_PLUGIN_ROOT/templates/* directly — plugin updates will overwrite those edits. This skill exists so customization lives inside the project. If the user is inside the plugin directory tweaking templates/b2b-ict/categories.json, stop them and route to this skill instead.
What ships with it
6 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.
- 6d ago First seen · 200 lines · 195 tokens per session scan A f76218e4b824
portfolio-taxonomy is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 195 tokens to every session and 3,931 once invoked, about $0.0010 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…