daisyui packages.docs.instructions.md

Project-specific guidance for building the daisyUI documentation website with SvelteKit, a web framework, and Svelte 5, a user-interface tool.

In plain words
What is it for?
Use it when adding or changing daisyUI docs, especially Svelte components and interactive pages.
Why use it?
It keeps documentation changes consistent with the project's required versions, syntax, and interaction patterns.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/saadeghi/daisyui/packages.docs
Clone the repo
git clone --depth 1 https://github.com/saadeghi/daisyui

Made for: GitHub Copilot.

Per session 94 This file is loaded in full into every session.
When invoked 94 The same file β€” it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00094 $0.00094
Opus 5 $0.00047 $0.00047
Sonnet 5 $0.00019 $0.00019
Haiku 4.5 $0.00009 $0.00009

Measured 2d ago against content hash cf24ff766407, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

daisyui packages.docs.instructions.md 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 2d 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.

.github/instructions/packages.docs.instructions.md Β· 11 lines

What it actually says

Instructions for developing daisyUI docs

  • This is the source code of daisyUI docs website. The website is built with SvelteKit 2 and Svelte 5
  • We only use Svelte 5 syntax and features (not Svelte 4)
  • For interactivity we use Svelte Runes
  • Use Context7 MCP server to find information about SvelteKit, Svelte
Changes

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.

  1. 2d ago First seen Β· 11 lines Β· 94 tokens per session scan A cf24ff766407

Subscribe to this mod's changes

daisyui packages.docs.instructions.md is an instructions file published in the GitHub repository saadeghi/daisyui (42,247 stars, last pushed 9d ago), licensed MIT. It adds 94 tokens to every session, 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.