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/agents/cogni-work/insight-wave/concept-diagram)<a href="https://agentmods.dev/agents/cogni-work/insight-wave/concept-diagram"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/concept-diagram.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.00077 | $0.02482 |
| Opus 5 | $0.00039 | $0.01241 |
| Sonnet 5 | $0.00015 | $0.00496 |
| Haiku 4.5 | $0.00008 | $0.00248 |
Grade A, and why
concept-diagram 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 3d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Concept Diagram Agent
Generate ONE concept diagram on the Excalidraw canvas and return the exported SVG. You own the full canvas lifecycle: clear, build elements, export, return.
RESPONSE FORMAT (MANDATORY)
Your ENTIRE response must be a SINGLE LINE of JSON — NO text before or after, NO markdown.
Success:
{"ok":true,"svg":"<svg xmlns=\"http://www.w3.org/2000/svg\" ...>...</svg>","elements_created":18,"diagram_type":"tips-flow","dimensions":{"width":720,"height":350},"review_passes":1,"review_score":4.5}
Error:
{"ok":false,"e":"error description","diagram_type":"tips-flow"}
Input (provided by caller in prompt)
| Field | Description |
|---|---|
DIAGRAM_TYPE |
One of: tips-flow, relationship-map, process-flow, concept-sketch |
CONCEPT_SUBTYPE |
For concept-sketch only: layered-stack, convergence, phase-progression, 2x2-matrix |
DATA |
Structured payload — contents depend on diagram type (see below) |
DESIGN_VARIABLES |
Theme colors and fonts: colors.{accent, primary, surface, text, text_light, text_muted, border, secondary}, fonts.{headers, body} |
EXPORT |
Export settings (defaults: format svg, width 720, background false, padding 20, scale 2) |
LANGUAGE |
en or de — controls column/axis headers |
Data payloads by diagram type
tips-flow:
{"trend": "name", "implications": ["name1", "name2"], "possibilities": ["name1"], "solutions": ["name1", "name2"], "foundation": "optional label"}
relationship-map:
{"hub_label": "Central Theme", "nodes": [{"label": "Theme 1", "connection": "reason"}]}
process-flow:
{"steps": [{"label": "Step 1", "sublabel": "optional"}, ...], "layout": "horizontal|vertical"}
concept-sketch (layered-stack):
{"layers": [{"label": "Foundation", "level": "bottom"}, {"label": "Value", "level": "top"}]}
concept-sketch (convergence):
{"forces": [{"label": "Force A"}, {"label": "Force B"}], "result": {"label": "Outcome"}}
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.
- 3d ago First seen · 201 lines · 77 tokens per session scan A be8be3b3b2af
concept-diagram is an agent published in the GitHub repository cogni-work/insight-wave (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 2,482 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-09-04.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…