Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/cogni-work/insight-wave/knowledge-dashboardnpx skills add cogni-work/insight-wave --skill knowledge-dashboardgit clone --depth 1 https://github.com/cogni-work/insight-waveWrote 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/knowledge-dashboard)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/knowledge-dashboard"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/knowledge-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 | $0.00124 | $0.05543 |
| Opus 5 | $0.00062 | $0.02772 |
| Sonnet 5 | $0.00025 | $0.01109 |
| Haiku 4.5 | $0.00012 | $0.00554 |
Grade A, and why
knowledge-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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Dashboard
Render a self-contained HTML dashboard for a bound cogni-knowledge base. This skill runs the vendored render_dashboard.py (and, for --graph, build_graph.py) from scripts/vendor/cogni-wiki/skills/wiki-dashboard/scripts/ natively against the bound wiki — resolved vendored-first via resolve_wiki_scripts(), the same posture knowledge-ingest uses for its engine helpers — then writes one extra markdown file (knowledge-overlay.md) that surfaces what binding.json knows but the bare wiki dashboard does not: which research projects have contributed, and what the latest lint audit said about claim drift. A standalone Karpathy base renders its dashboard with no cogni-wiki plugin installed.
The cogni-knowledge value-add over a raw wiki-dashboard render is:
- Binding-aware wiki path resolution — no
--wiki-rootfrom the user. - Knowledge overlay sidecar — a markdown file co-located with
wiki-dashboard.htmlthat captures the binding view: a deposited-projects table with per-project inverted-pipeline depth (sub-questions, fetched/unavailable, distilled concepts + claim-dedup ratio, verifier verdicts), a knowledge-base-global fetch-cache health block, and the latest lint-audit summary.
Read ${CLAUDE_PLUGIN_ROOT}/references/delegation-contract.md once per session to remember the boundary — this skill writes only one file (knowledge-overlay.md); the HTML render (wiki-dashboard.html / wiki-graph.html) is the vendored dashboard scripts' responsibility.
When to run
- User asks for a dashboard or HTML view of a bound knowledge base
- After several pipeline deposits, to see the shape of the accumulated wiki
- Before sharing a knowledge base with a colleague — the dashboard + overlay are both single files
Never run when
- No
binding.jsonexists at the resolved knowledge root — route to/cogni-knowledge:knowledge-setup. (A raw wiki with no binding is rendered byrender_dashboard.pydirectly; this skill adds the binding overlay.) - The wiki is empty —
render_dashboard.pystill renders an honest empty dashboard, and the overlay renders honestly with zero deposits.
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 · -13 lines 8c4a7d6a8d30
- 4d ago First seen · 296 lines · 124 tokens per session scan A 087d66ee427e
knowledge-dashboard is a skill published in the GitHub repository cogni-work/insight-wave (12 stars, last pushed today), licensed Apache-2.0. It adds 124 tokens to every session and 5,543 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…