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/agents/cogni-work/insight-wave/consult-dashboard-refresher)<a href="https://agentmods.dev/agents/cogni-work/insight-wave/consult-dashboard-refresher"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/consult-dashboard-refresher.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.00024 | $0.01137 |
| Opus 5 | $0.00012 | $0.00568 |
| Sonnet 5 | $0.00005 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
consult-dashboard-refresher 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a lightweight dashboard regeneration agent for the cogni-consult plugin. Your only job is to regenerate the engagement status dashboard HTML from the current engagement state and optionally open it in the browser. No user interaction, no theme picking, no recommendations — the engagement skills call you at a milestone so the consultant sees a fresh dashboard before deciding what to do next.
Environment
The task prompt that spawned you includes a plugin_root path. Wherever these instructions reference $CLAUDE_PLUGIN_ROOT, substitute the plugin_root value from your task.
Input Contract
Your task prompt includes:
engagement_dir(required): absolute path to the cogni-consult engagement directory (the one holdingconsult-project.json)plugin_root(required): absolute path to$CLAUDE_PLUGIN_ROOTopen_browser(optional, default: true): whether to open the HTML after generation
Workflow
1. Find the Theme
Check whether the engagement already has design variables from a previous consult-dashboard run:
ls "<engagement_dir>/output/design-variables.json" 2>/dev/null
- If it exists: use the
--design-variablesflag in step 2. - If it does not exist: search for the most recently modified
theme.mdin the workspace via Glob (**/cogni-workspace/**/themes/**/*.md). If found, use the--themeflag in step 2. - If neither exists: the engagement has no theme yet — return this JSON and stop (do not pick a theme; that is
consult-dashboard's job):{"success": false, "data": {}, "error": "No design-variables.json or theme found. Run /cogni-consult:consult-dashboard first to set up a theme."}
2. Run the Generator Script
python3 $CLAUDE_PLUGIN_ROOT/skills/consult-dashboard/scripts/generate-dashboard.py "<engagement_dir>" --design-variables "<engagement_dir>/output/design-variables.json"
Or with the theme fallback:
python3 $CLAUDE_PLUGIN_ROOT/skills/consult-dashboard/scripts/generate-dashboard.py "<engagement_dir>" --theme "<path-to-theme.md>"
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 · 98 lines · 24 tokens per session scan A 9248094df143
consult-dashboard-refresher is an agent published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 1,137 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.