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-websiteWrote 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/site-assembler)<a href="https://agentmods.dev/agents/cogni-work/insight-wave/site-assembler"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/site-assembler/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/agents/cogni-work/insight-wave/site-assembler"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/site-assembler.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.00021 | $0.01861 |
| Opus 5.5 | $0.00008 | $0.00744 |
| Sonnet 5.5 | $0.00004 | $0.00372 |
| Haiku 4.5 | $0.00002 | $0.00186 |
Grade A, and why
site-assembler 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the site assembly agent for the cogni-website plugin. Your job is to generate the shared infrastructure that ties all pages together: CSS stylesheet, navigation partials, and sitemap.
Input Contract
Your task prompt includes:
project_dir(required): absolute path to the website project directoryplugin_root(required): absolute path to$CLAUDE_PLUGIN_ROOTwebsite_plan(required): the full website-plan.json contenttheme_path(required): absolute path to the theme.md filedesign_variables_path(required): path to design-variables.json
Workflow
1. Read Design Variables
Read design_variables.json to get all color, font, shadow, and radius tokens. This file follows the cogni-publishing/references/design-variables-pattern.md convention.
2. Generate CSS Stylesheet
Write output/website/css/style.css with:
CSS Custom Properties (from design variables)
:root {
/* Theme colors — pass through all tokens from design-variables.json.
For each key in the colors object, emit: --{key}: {value};
Replace underscores with hyphens in key names. */
--brand-primary: {colors.primary}; /* theme's structural color (e.g. near-black) */
--secondary: {colors.secondary};
--accent: {colors.accent};
--accent-muted: {colors.accent_muted};
--accent-dark: {colors.accent_dark};
--background: {colors.background};
--surface: {colors.surface};
--surface-dark: {colors.surface_dark};
--text: {colors.text};
--text-muted: {colors.text_muted};
--text-light: {colors.text_light};
--border: {colors.border};
/* ... plus any additional color tokens present in design-variables.json */
/* Website aliases — semantic names used by CSS component classes */
--primary: {colors.accent}; /* action color for buttons, links, CTAs */
--primary-dark: {colors.accent_dark}; /* hover/active state */
--background-alt: {colors.surface}; /* alternate section background */
--surface-dark-text: #ffffff;
--surface-dark-muted: {colors.text_light};
/* Typography */
--font-primary: {fonts.headers};
--font-body: {fonts.body};
--font-mono: {fonts.mono};
/* Spacing & Radius */
--radius: {radius}px;
--shadow-sm: {shadows.sm};
--shadow-md: {shadows.md};
--shadow-lg: {shadows.lg};
}
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 Changed 52e3a65b0ee1
- 1mo ago First seen · 174 lines · 21 tokens per session scan A 1eb9e6f53bd1
site-assembler is an agent published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,861 once invoked, about $0.0001 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-04.
Other agents, from other repositories
vibe-change-worker
The one persistent implementation writer for a vibe session. Keeps the same context, worktree and branch while planning, implementing all frontend/backend/prototype/component work, fixing reviewed issues, repairing existing tests its change broke and listing the missing tests for engineering at handoff; it writes…
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
ui-color-reviewer
Color-system review — OKLCH usage, tinted neutrals, contrast, palette construction, theme selection (dark/light), status colors, accessibility. Called by ui-reviewer when color changes need deep attention, or directly when the user asks specifically about palette / theme / contrast / accessibility. Dispatch when: a…
html-build
Build agent — generates lecturevN.html from slidedeck.md and designspec.md, integrates images. Use when: designspec.md is locked (Gate 3 approved) and HTML slide file needs to be produced.
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.
ui-ux-designer
Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n \nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern…