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/darcos-loft/fluid/outputnpx skills add Darcos-Loft/fluid --skill outputgit clone --depth 1 https://github.com/Darcos-Loft/fluidWrote 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/darcos-loft/fluid/output)<a href="https://agentmods.dev/skills/darcos-loft/fluid/output"><img src="https://agentmods.dev/badge/skills/darcos-loft/fluid/output.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.00044 | $0.00318 |
| Opus 5 | $0.00022 | $0.00159 |
| Sonnet 5 | $0.00009 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
output 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.
What it actually says
Output
The difference between a demo and a shippable build is finish. This is a short checklist the agent runs before calling UI work done.
No placeholders
- No "lorem ipsum", no "TODO", no "[image here]", no empty
href="#". Use real or plausible content. - No "rest of the component" comments, no skipped sections. Write the whole thing.
Every state
- Loading, empty, error, and success states for anything that fetches or submits.
- Hover, focus-visible, active, and disabled for every interactive element.
- Responsive: the layout holds at 375px, 768px, and 1280px. No horizontal scroll on mobile.
Honest completeness
- If the brief lists five sections, build five, fully. Do not stub the last two.
- Every link goes somewhere. Every button does something or is clearly disabled.
- Accessibility: alt text, labels, visible keyboard focus, body contrast 4.5:1.
Pre-flight
Before saying it is done, re-read the brief and confirm each requirement is actually met, not approximated. Run the fluid detector. If anything is stubbed, finish it first.
Pairs with: every other skill. This is the last gate before shipping.
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 · 29 lines · 44 tokens per session scan A b4e9255039a6
output is a skill published in the GitHub repository Darcos-Loft/fluid (3 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 318 once invoked, about $0.0002 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
extract-design
Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
morphous-catalog
Create or refresh Morphous website design-system/theme bundles from animal, insect, plant, landscape, mineral, weather, or other nature motifs. Use when Codex is asked to generate Morphous motif images, light/dark design-system boards, reusable image prompts, generated web assets, shadcn/tweakcn theme exports, or the…
brandmd
Extract a website's design system into a DESIGN.md file. Use when starting a new frontend project, rebuilding a site, or when the user wants AI-generated UI to match an existing brand.
google-fonts
Google Fonts typography system generator. Suggests single fonts (strict mode) and font pairs (contrast mode) with complete typographic scales following Tailwind Typography rhythm concepts. Generates CSS custom properties, Tailwind config, and embed links. Trigger: "choose a font", "font pairing", "typography system"…
uisandbox
Open a real, built web app in UISandbox — the interactive sandbox in the user's browser, 1:1, with the app's own knobs (brand, colours, fonts, radius, spacing…) — or test one change headlessly, verify it still renders 1:1, get a screenshot and the patch. Use when someone wants to look at their app in a sandbox and…