daisyUI is a library of ready-made interface components built for Tailwind CSS, a utility-based system for styling web pages. It helps web developers assemble consistent buttons, forms, navigation, and other UI elements. The catalogue entries provide add-ons for working with this component library.
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/saadeghi/daisyui/find-bugsnpx skills add saadeghi/daisyui --skill find-bugsgit clone --depth 1 https://github.com/saadeghi/daisyuiWrote 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/saadeghi/daisyui/find-bugs)<a href="https://agentmods.dev/skills/saadeghi/daisyui/find-bugs"><img src="https://agentmods.dev/badge/skills/saadeghi/daisyui/find-bugs.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.00101 | $0.01851 |
| Opus 5 | $0.00051 | $0.00925 |
| Sonnet 5 | $0.00020 | $0.00370 |
| Haiku 4.5 | $0.00010 | $0.00185 |
Grade A, and why
find-bugs 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 5d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Finder
Find only evidence-backed product bugs and leave the user with a plan they can approve or reject. Do not implement the plan.
Required agent routing
- If you are not the
bug_findercustom agent, delegate the complete task tobug_finderand wait for its result. Tell the agent to use this skill. Do not investigate the bug or write the plan in the current agent. - If you are the
bug_findercustom agent, perform this workflow directly. Do not delegate it again. - If
bug_finderis not available, stop and report the problem. Do not run this workflow with a different agent or model.
Non-negotiable boundary
- Treat the repository as read-only except for the final
tmp/bugs/*.mdplan files. - Do not edit source, tests, snapshots, fixtures, generated package files, build output, config, translations, dependencies, lockfiles, or Git metadata.
- Do not create a temporary reproduction inside
packages/. Put disposable fixtures, logs, and screenshots in an OS temporary directory. - Do not run formatters, auto-fixers, write-mode generators, dependency installers, release commands, or publishing commands.
- Do not create a branch, commit, PR, issue, comment, or other external side effect.
- Do not provide a patch or replacement code. Describe the intended behavior and future change boundary in prose.
- Stop after writing the plan. The user decides whether implementation should happen.
Normal tests, local servers, and read-only diagnostics are allowed. Prefer commands that do not write into the repository. Before running any command, determine whether it creates build output or generated files. If it does, use an OS-temporary copy or a non-writing alternative; otherwise record that verification as pending. Never overwrite or clean up a user's files.
Load the relevant guidance
- Read
packages/AGENTS.md. - Read the target package's
AGENTS.md. - Read references/daisyui.md for
packages/daisyui. - Read references/docs.md for
packages/docs. - Read both package references when ownership is unclear or the defect crosses the package boundary.
- Read references/bug-plan.md before creating or updating a plan.
What ships with it
3 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.
- 5d ago First seen · 168 lines · 101 tokens per session scan A d804195981e1
find-bugs is a skill published in the GitHub repository saadeghi/daisyui (42,247 stars, last pushed 11d ago), licensed MIT. It adds 101 tokens to every session and 1,851 once invoked, about $0.0005 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-30.
Other skills, from other repositories
frontend-clean-ui
Activate when designing, building, or refactoring modern, accessible, high-contrast web user interfaces, SaaS dashboards, and landing pages with Tailwind CSS, design tokens, dark mode, and responsive flex/grid layouts — trigger phrasings include "build a modern UI for my web app", "redesign this dashboard to look…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
seed-changeset
SEED 저장소의 현재 Git 변경에서 공개 패키지 후보와 기존 changeset 포함 여부를 찾고, 사용자 확인을 거쳐 패키지 bump와 한국어 changeset 메시지를 작성한다. peer dependency 범위, 브랜치, 배포는 변경하지 않는다.
conversational-ux
Design voice and conversational interfaces — dialog flows, error recovery, and persona. Use when the interface speaks and listens rather than being tapped. For graphical input collection, use form-design.
form-design
Design a form end to end — field order, grouping, validation, and completion. Use when the artifact is a form. For product-wide error strategy use error-handling-ux; for first-run signup use onboarding-design.