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 instructions/saadeghi/daisyui/communicationgit clone --depth 1 https://github.com/saadeghi/daisyuiWhat 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.00086 | $0.00086 |
| Opus 5 | $0.00043 | $0.00043 |
| Sonnet 5 | $0.00017 | $0.00017 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
daisyui communication.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 yesterday.
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
Communication Rules
- Do not explain things unless asked
- Do not confirm nor deny anything unless you are 100% sure
- Always fact check your answers
- If you are unsure about something, say "I don't know"
- Do not write intros like "I will help you with this", etc. Just do the task
- Do not write conclusions or summaries unless asked
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.
- yesterday First seen · 13 lines · 86 tokens per session scan A 60e7d165407e
daisyui communication.instructions.md is an instructions file published in the GitHub repository saadeghi/daisyui (42,247 stars, last pushed 8d ago), licensed MIT. It adds 86 tokens to every session, about $0.0004 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 instructions, from other repositories
starwind-ui AGENTS.md
Instructions for starwind-ui/starwind-ui, covering agents.md, project shape, useful commands and contribution conventions.
fundamental-ngx AGENTS.md
Instructions for SAP/fundamental-ngx, covering angular 22+ development guidelines, persona, quick reference, essential commands and build/lint/test specific library.
wonder-blocks CLAUDE.md
Instructions for Khan/wonder-blocks, covering wonder blocks design system, technology stack, coding conventions, file & export naming and typescript.
wonder-blocks storybook.instructions.md
Storybook best practices for Wonder Blocks component stories.
wonder-blocks AGENTS.md
Instructions for Khan/wonder-blocks, covering wonder blocks – agentic workflows & storybook mcp, installing the mcp (consumer setup), storybook mcp server, when it’s available and mcp endpoint.
openbridge-webcomponents watch-radial-instruments.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering watch & radial instruments, architecture overview, key principle: logic in watch.ts, instruments stay thin, shared sibling modules and layering & stacking pattern.