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-consolidate)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/portfolio-consolidate"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/portfolio-consolidate/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-consolidate"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/portfolio-consolidate.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.00117 | $0.01677 |
| Opus 5 | $0.00059 | $0.00839 |
| Sonnet 5 | $0.00023 | $0.00335 |
| Haiku 4.5 | $0.00012 | $0.00168 |
Grade A, and why
portfolio-consolidate 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 8d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portfolio Consolidate (Phase 1)
Roll up multiple portfolio-scan outputs — typically research-only scans of peer companies in the same industry — into one taxonomy-shaped coverage matrix. The output is a markdown pivot table {company × category_id} plus a sibling JSON so downstream tooling can reason about cross-provider coverage.
Core Concept
Every portfolio-scan writes research/.metadata/scan-output.json plus a markdown report that tags each taxonomy category with a [Status: X] marker (Confirmed / Not Offered / Emerging / Extended). When you scan several companies in the same taxonomy, those per-company reports answer "what does each provider cover?" but they live in separate directories. This skill joins them into one table so the reader can see — at a glance — who covers which category and where the peer-group whitespace sits.
Complementary boundary with compete
compete— proposition/messaging level (Feature × Market). Runs after propositions exist; produces battle cards and competitive-response messaging.portfolio-consolidate— taxonomy/capability level (Company × Category). Runs on raw scan output; produces a provider-set coverage matrix.
If the user is asking "who offers what", use this skill. If they are asking "how do I win against provider X on proposition Y", use compete.
Scope (Phase 1)
Phase 1 ships the minimum useful slice:
- Two cell states —
✓(Confirmed; includes Emerging and Extended) and—(Not Offered or not reported). - Per-category coverage rate (count of
✓cells over the provider set). - Hard refuse on
template_typemismatch across inputs. - Single output pair per invocation —
research/consolidated-{scope-slug}-portfolio.mdplusresearch/.metadata/consolidated-{scope-slug}.json.
Deferred to follow-up issues: separate Emerging / Extended cell states, per-dimension executive summary, whitespace / gap analysis by category, leaders / laggards callouts, and portfolio-dashboard integration. Do not extend the script beyond Phase 1 inside this skill — follow-up issues will track those additions.
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.
- 8d ago First seen · 108 lines · 117 tokens per session scan A a366a85456e0
portfolio-consolidate is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 117 tokens to every session and 1,677 once invoked, about $0.0006 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…
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…
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…