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-resume)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/portfolio-resume"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/portfolio-resume/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-resume"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/portfolio-resume.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.00086 | $0.05215 |
| Opus 5.5 | $0.00034 | $0.02086 |
| Sonnet 5.5 | $0.00017 | $0.01043 |
| Haiku 4.5 | $0.00009 | $0.00522 |
Grade B, and why
portfolio-resume scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Discover portfolio projects in the workspace using the discovery script. The script resolves the workspace root automatically (priority: `--root` > `$PROJECT_AGENTS_OPS_ROOT` > walk-up from `$PWD` to find a `cogni-portfo How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portfolio Resume
Session entry point for returning to portfolio work. This skill orients the user by showing where they left off and what to do next.
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.
Portfolio projects span multiple sessions, and without a clear re-entry point users lose context between them. This skill reads the project state, surfaces progress at a glance, and recommends the most valuable next step.
Workflow
1. Find Portfolio Projects
Discover portfolio projects in the workspace using the discovery script. The script resolves the workspace root automatically (priority: --root > $PROJECT_AGENTS_OPS_ROOT > walk-up from $PWD to find a cogni-portfolio/ ancestor > $PWD), scans it for cogni-portfolio/*/portfolio.json, and also returns projects from the global registry (~/.claude/cogni-portfolio-projects.json) so workspaces hosted outside the insight-wave repo (OneDrive, Dropbox, client folders) surface even when cwd is unrelated.
bash "${CLAUDE_PLUGIN_ROOT:-$(ls -td "$HOME"/.claude/plugins/cache/insight-wave/cogni-portfolio/*/ | head -1)}/scripts/discover-projects.sh" --json
Returns JSON with count, search_root, and a projects array. Each project entry includes path (absolute), slug, company_name, company_industry, language, updated, and pipeline-stage flags (has_products, has_features, has_markets, has_propositions, has_solutions, has_dashboard). Pass path verbatim — absolute — to every subsequent script call; never reconstruct it from $PWD.
If count is 0:
- First, ask the user if they have a project in a different directory (e.g., OneDrive, external workspace). If they provide a path, register it once and re-run discovery:
Surface the detectedbash "${CLAUDE_PLUGIN_ROOT:-$(ls -td "$HOME"/.claude/plugins/cache/insight-wave/cogni-portfolio/*/ | head -1)}/scripts/discover-projects.sh" --register "<path>"search_rootin your prompt so the user can see where discovery looked: "I checked<search_root>and didn't find a portfolio. Is the project somewhere else?" - If the user confirms no project exists yet, briefly tell them "No portfolio project exists in this workspace yet — let's set one up" (in their language if known) and dispatch the
portfolio-setupskill via the Skill tool to begin initialization. Do not ask the user to re-issue a command; the handoff should be seamless. Once setup completes, control returns here naturally — the user can re-invoke/portfolio-resumeto see the new project's status, or simply continue with the next-step recommendations setup printed.
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 First seen · 184 lines · 86 tokens per session scan B b862a370e9f2
portfolio-resume is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 86 tokens to every session and 5,215 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
dx-optimizer
Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.
document-actions
Extract cited facts, obligations, deadlines and proposed actions from documents, preserving OCR uncertainty and reconciling Prismer tasks.