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-workspaceWrote 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/install-mcp)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/install-mcp"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/install-mcp/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/install-mcp"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/install-mcp.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.00235 | $0.03284 |
| Opus 5.5 | $0.00094 | $0.01314 |
| Sonnet 5.5 | $0.00047 | $0.00657 |
| Haiku 4.5 | $0.00023 | $0.00328 |
Grade A, and why
install-mcp 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install MCP
Why This Exists
Plugins in insight-wave depend on MCP servers (Excalidraw for diagrams, Pencil for web rendering, etc.). No plugin declares a server itself. A checked-in declaration asserts machine state the repository cannot guarantee, so on a machine that never installed the server it is spawned at session start and fails visibly. The server is therefore installed on demand and written into the user's own config, which is the one place that can honestly say what is available. Git-based MCPs also need cloning and building, and users of either client used to have to edit that config by hand.
This skill handles the full lifecycle: detect what's needed, install it, configure it for the user's environment, and verify it works. No manual JSON editing required.
Detect Environment
Determine the user's runtime environment — this affects what needs patching:
-
Locate the config to write. Claude Code reads a user-scope config; Claude Desktop reads its own. Check both:
- Claude Code (all platforms):
~/.claude.json, top-levelmcpServers - Claude Desktop, macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Claude Desktop, Linux:
${XDG_CONFIG_HOME:-~/.config}/Claude/claude_desktop_config.json - Claude Desktop, Windows:
%APPDATA%/Claude/claude_desktop_config.json
Only the top-level
mcpServersin~/.claude.jsonis user scope. The per-projectprojects.<path>.mcpServersobjects in that same file are local scope — never write there, or the server disappears the moment the user changes directory. - Claude Code (all platforms):
-
Classify environment:
- Claude Code CLI — needs the git install AND a
--target cliwrite to~/.claude.json. - Claude Desktop — needs the git install AND a
--target desktopwrite. - Both — Desktop config exists alongside CLI usage. Use
--target both.
- Claude Code CLI — needs the git install AND a
Record the classification as MCP_TARGET, whose only legal values are cli, desktop
and both. The write step below sets and consumes it in a single shell — each invocation
gets a fresh environment, so an assignment made here would not survive to reach it.
What ships with it
2 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.
- 1mo ago First seen · 299 lines · 235 tokens per session scan A 763b0c2ed018
install-mcp is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 235 tokens to every session and 3,284 once invoked, about $0.0009 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-14.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.