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 waveriderai/ce-design-flow/plugin install ce-design-flowWrote 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/waveriderai/ce-design-flow/ce-markup)<a href="https://agentmods.dev/skills/waveriderai/ce-design-flow/ce-markup"><img src="https://agentmods.dev/badge/skills/waveriderai/ce-design-flow/ce-markup.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.00152 | $0.01453 |
| Opus 5 | $0.00076 | $0.00727 |
| Sonnet 5 | $0.00030 | $0.00291 |
| Haiku 4.5 | $0.00015 | $0.00145 |
Grade A, and why
ce-markup 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CE Markup — the browser round trip
One job: hand the artifact to the human in a live browser, and pick it back up correctly when they return. This is a re-entrant step — call it at any gate (wireframe review, hi-fi review, or verifying a built UI against its mockup), as many times as you need.
Why it needs a skill at all
The failure mode is not opening the browser. It is coming back. The agent remembers the state of the file as of before the human edited it, then keeps working from that stale memory — silently discarding what the human just did. Everything below exists to prevent that one bug.
Going out
- Identify the artifact: project id + file name. If you just finished a run, that is the
run's project and the
*.htmlin the project root. If unsure, list the project's files and pick by mtime. - Resolve the portal host — never hardcode it:
PrintsOD_HOST=$("$CLAUDE_PLUGIN_ROOT/scripts/od-host.sh")127.0.0.1when you are local. Prints the machine's LAN/Tailscale address when you are working over SSH — because the browser runs on your laptop, andlocalhostthere would point at the wrong machine. - Print the URL and stop.
Say plainly what the human can do there, and that you will wait:http://$OD_HOST:60301/projects/<projectId>/files/<file.html>Open this and change whatever you want — chat with the agent in the composer, or use markup/comments to click an element and describe the change. Edits save straight to the project file. When you're done, come back and say "continue".
- Do not poll, do not guess, do not keep working. The human is the gate.
What the human can do in there
| In the portal | What it does |
|---|---|
| Type in the composer | Conversational iteration with the inner agent, in that project's conversation |
| Markup / comment on an element | Pin a comment to a specific element, then describe the change |
| Manual edit mode | Edit the artifact directly, no agent involved |
| "Choose design system" dropdown | Swap the brand skin (takes effect at hi-fi; wireframe templates ignore it) |
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 · 103 lines · 152 tokens per session scan A e3500a9e1358
ce-markup is a skill published in the GitHub repository waveriderai/ce-design-flow (1 stars, last pushed 1mo ago), licensed MIT. It adds 152 tokens to every session and 1,453 once invoked, about $0.0008 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-31.
Other skills, from other repositories
system-pitch
Write a design system investment pitch with a business case and ROI framing. Trigger when someone says: pitch the design system, make the case for the system, sell this to leadership, justify the investment, business case for design systems, why should we invest in a design system, or anything about building an…
ai-component-description
Generate AI-optimised text descriptions for components, formatted for Figma's MCP server and LLM consumption. This produces prose descriptions in a six-section format (purpose, props, anti-patterns, composition, accessibility, examples), NOT JSON schemas or structured data files. Trigger when someone says: write…
context-engine-builder
Generate a context engine — seven structured blueprint files (UX, UI, content, accessibility, ethical, technical, business intelligence) that encode everything an AI agent needs to work with a design system. This produces YAML infrastructure in .ai/context-engine/, NOT a health score or quality assessment. Trigger…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
token-compliance
Check a codebase or implementation for token compliance — finding hardcoded values, wrong-tier token references, and inconsistent token application in consuming code. This checks how tokens are used in code, NOT how the tokens themselves are defined or structured. Trigger when someone says: are we using tokens…