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 skills add lukedj78/dev-flow --skill coss-uigit clone --depth 1 https://github.com/lukedj78/dev-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/lukedj78/dev-flow/coss-ui)<a href="https://agentmods.dev/skills/lukedj78/dev-flow/coss-ui"><img src="https://agentmods.dev/badge/skills/lukedj78/dev-flow/coss-ui/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/skills/lukedj78/dev-flow/coss-ui"><img src="https://agentmods.dev/badge/skills/lukedj78/dev-flow/coss-ui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00244 | $0.02428 |
| Opus 5.5 | $0.00098 | $0.00971 |
| Sonnet 5.5 | $0.00049 | $0.00486 |
| Haiku 4.5 | $0.00024 | $0.00243 |
Grade A, and why
coss-ui 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
coss-ui — Coss/UI (Cal.com design system) for a dev-flow project
This skill owns the Coss/UI side of a web project: installing and extending Coss components (the Cal.com design system on Base UI + Tailwind v4) through the shadcn CLI @coss/* registry, and keeping Coss's tokens reconciled with the project's DESIGN.md. It composes with design-md-to-app (which owns the generic Next.js scaffold) — it does not re-implement it.
The one rule that matters most
Never invent the Coss commands or registry. The source of truth is the live docs at https://coss.com/ui/docs (get-started + each component page shows its exact pnpm dlx shadcn@latest add @coss/<name> command) and the repo cosscom/coss. Confirm the exact command, the components.json#registries config for the @coss namespace, and the current registry URL before running anything. Coss is young; treat this skill as the workflow + conventions, not a frozen copy of the API. Swept 2026-08-26 against the live registry (coss.com/ui/r/registry.json — 577 items — plus style.json, ui.json and the three font items), so the counts, the namespace requirement and the font slots below are read from the registry rather than the docs page. Anything still marked [VERIFY] must be checked against the live docs first.
Why Coss fits dev-flow (and when to pick it)
Coss/UI rides the same machinery dev-flow already uses: shadcn CLI v4 + components.json + CSS-variable tokens with the same names as shadcn/ui. So the DESIGN.md → tokens pipeline works unchanged; Coss just supplies the default token set (@coss/colors-neutral) plus a curated Base-UI component/particle registry. It is a UI-library choice inside the shadcn / Base-UI family, recorded as stack.ui = "coss" (with ui_base = "base", since Coss is built on Base UI).
Pick Coss when the user wants the Cal.com aesthetic/DX, a Base-UI foundation, and an AI-first copy-paste kit. Two caveats make it a deliberate choice, not a default:
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 d0e621d5673c
- 1mo ago First seen · 96 lines · 244 tokens per session scan A cf68b85cf816
coss-ui is a skill published in the GitHub repository lukedj78/dev-flow (6 stars, last pushed yesterday), licensed MIT. It adds 244 tokens to every session and 2,428 once invoked, about $0.0010 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-08-31.
Other skills, from other repositories
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
design-craft
Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique. Use for new screens, landing pages, redesigns, typography/layout work, or UI that feels generic or AI-generated. For small fixes, preserve the existing design without starting a…
design-critique
Use this skill to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states, accessibility and copy, ending in a ranked fix list. Triggers: user says "review the design", "critique this UI", "why does this…
accessibility
Implement and review accessible user interfaces with semantic controls, keyboard and focus behavior, readable content and assistive-technology checks. Use when fixing inaccessible forms, dialogs, navigation, drag interactions or WCAG gaps; distinguish automated findings from tested accessibility.
component-design
Apply a coherent visual system, responsive behavior, interaction states, and accessibility to Kun components.