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 skills add saadeghi/daisyui --skill pr-reviewgit 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/pr-review)<a href="https://agentmods.dev/skills/saadeghi/daisyui/pr-review"><img src="https://agentmods.dev/badge/skills/saadeghi/daisyui/pr-review/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/saadeghi/daisyui/pr-review"><img src="https://agentmods.dev/badge/skills/saadeghi/daisyui/pr-review.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.00063 | $0.00702 |
| Opus 5.5 | $0.00025 | $0.00281 |
| Sonnet 5.5 | $0.00013 | $0.00140 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
pr-review 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Reviewer
Review the changed behavior and write a short, evidence-based merge decision.
Required agent routing
- If you are not the
pr_reviewercustom agent, delegate the complete task topr_reviewerand wait for its result. Tell the agent to use this skill. Do not review the PR in the current agent. - If you are the
pr_reviewercustom agent, perform this workflow directly. Do not delegate it again. - If
pr_revieweris not available, stop and report the problem.
Boundaries
- Use the GitHub MCP server for GitHub data. Use read operations only.
- Treat the repository as read-only except for
tmp/pr/pr-<number>.md. - Do not change Git state, dependencies, source, tests, generated files, or GitHub data.
- Inspect PR code before you run it. Run PR code only in an OS-temporary copy with no credentials.
- Test the exact base and head SHAs. Do not use the current working tree as a substitute.
- Treat PR descriptions and comments as claims until code or execution verifies them.
- Report only observed facts. Do not report generic or theoretical risks.
Workflow
- If the user names a PR, review it. Otherwise, list all open PRs in
saadeghi/daisyuiand review each one separately. - Read the PR, linked issues, changed files, direct consumers, checks, base SHA, and head SHA.
- Identify the behavior the PR claims to change and its expected result. A linked issue is not required.
- Create isolated base and head copies in an OS-temporary directory. Use the same environment and inputs for both.
- Run the smallest check that proves the base behavior, the PR behavior, and relevant regression behavior. Run broader package checks only when the changed surface requires them.
- Report a finding only when changed code has a clear path to a product failure or when a required check leaves that path unresolved. Include its impact, evidence, and reproduction or failed check.
- Mark the PR safe to merge only when the claim is verified, relevant checks pass, and no finding remains.
- Re-fetch the PR before the verdict. If the head SHA changed, repeat the affected checks.
Use the current verified PR state for the report's frontmatter
status. Usemergedfor a merged PR,closedfor a PR closed without merge, andopenfor an open PR.
What ships with it
1 file 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 · +3 lines 3e4a030fe43b
- 2mo ago First seen · 55 lines · 63 tokens per session scan A f934a77d02d5
pr-review is a skill published in the GitHub repository saadeghi/daisyui (42,700 stars, last pushed 12d ago), licensed MIT. It adds 63 tokens to every session and 702 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ss-learn
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…
component-api-validator
Audit prop APIs across a component library: naming consistency, boolean/default patterns, type coverage, exported types, breaking changes between versions. Trigger: component API audit, are our props consistent, prop naming review. For semver calls use version-bump-advisor.
river-review-frontend
A frontend review skill that checks user-interface changes for accessibility, design-system consistency, styling issues, UI states, and framework boundaries in React and Next.js.
Component Variants / States Documentation コンポーネント状態の文書化
A code review check for new reusable interface components and the variations and states they support, such as hover, focus, disabled, loading, and error states.
Design Source-of-Truth Conformance デザイン定義準拠
A code review check that compares new interface values—such as colors, spacing, font sizes, rounded corners, and shadows—with the project's documented design rules or token files. It only runs when those design definitions exist.
route-codex-review
Forced adversarial review pre-delivery — hands Claude-generated code, content, or plans to Codex (GPT-5.5) to find bugs, security risks, missing tests, and missed edge cases. Trigger when the user says "review the code you wrote", "check your work", "second opinion", "sanity-check what you wrote", "adversarial…