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-consultWrote 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/consult-dashboard)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/consult-dashboard"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/consult-dashboard.svg" alt="Measured on agentmods" 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.00088 | $0.03085 |
| Opus 5 | $0.00044 | $0.01543 |
| Sonnet 5 | $0.00018 | $0.00617 |
| Haiku 4.5 | $0.00009 | $0.00309 |
Grade A, and why
consult-dashboard 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 today.
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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consult Dashboard
Generate a self-contained HTML dashboard that visualizes a consulting engagement's
status — the action-field work breakdown, every deliverable's state and
design-thinking stage, acting-persona review progress, knowledge-base linkage, and
the recommended next action. The dashboard opens in the browser and is the visual
sibling of the text WBS table that consult-resume and consult-action-fields
render inline.
Core Concept
Engagement status lives in consult-project.json plus one field.json per action
field, where each deliverable carries its own state, dt_stage, and
persona_review. The text WBS table is good for a quick check; this dashboard is for
visual exploration — scanning field-by-field progress, spotting which deliverables are
stuck mid-loop, and seeing persona-review coverage at a glance.
Deliverable state is the single source of truth (it lives only in field.json);
field and engagement completion are derived at read time, never stored. The
generator is read-only — it never modifies any engagement file.
Workflow
0. Resolve the Interaction Language
Before any user-facing output, resolve the interaction language — the
workspace default, overridden by the user's message language — per
$CLAUDE_PLUGIN_ROOT/references/interaction-language.md, which owns the
resolution ladder. Conduct the entire conversation in the resolved language.
It is independent of the engagement's language field, which is the
deliverable axis. This contract holds on the default path: it does not depend
on an output style being active.
The description of a Bash tool call is rendered to the consultant, so it is
user copy — write it in the interaction language, outcome-shaped, at most 6
words, with no script, file, or skill names, and never derived from the
script's filename or header comment. Worked pair:
Discover cogni-consult engagements → Laufende Engagements holen.
Section (f) of the canonical ecosystem register owns these five constraints —
edit them there first, then mirror into
$CLAUDE_PLUGIN_ROOT/references/user-facing-output.md and here.
What ships with it
3 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.
- today Changed 32e946cc8c47
- 4d ago Changed · +5 lines fa3debfe4333
- 8d ago First seen · 214 lines · 88 tokens per session scan A 7236ca996e58
consult-dashboard is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 88 tokens to every session and 3,085 once invoked, about $0.0004 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-08-30.
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…
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…
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…