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.
Borrowing it
Nothing to install: this file belongs to saadeghi/daisyui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/saadeghi/daisyui/master/.github/instructions/code_generation_with_git.instructions.mdgit 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/instructions/saadeghi/daisyui/code_generation_with_git)<a href="https://agentmods.dev/instructions/saadeghi/daisyui/code_generation_with_git"><img src="https://agentmods.dev/badge/instructions/saadeghi/daisyui/code_generation_with_git/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/instructions/saadeghi/daisyui/code_generation_with_git"><img src="https://agentmods.dev/badge/instructions/saadeghi/daisyui/code_generation_with_git.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01006 | $0.01006 |
| Opus 5.5 | $0.00402 | $0.00402 |
| Sonnet 5.5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
daisyui code_generation_with_git.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 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rules for using Git branches during code generation sessions
Activation
- These rules are ONLY applied when the user explicitly says "#usegit"
- If "#usegit" is not mentioned explicitly with the exact phrase, ignore these rules completely
Initial Setup
- Create a new feature branch with timestamp:
git checkout -b LLM/[$(date +%Y%m%d)]-[TASKNAME]- Replace
[TASKNAME]with a short descriptive name of the task - Example:
git checkout -b LLM/20241005-add-authentication
- Replace
- Confirm branch creation and inform user of the branch name
- Auto-stash any uncommitted changes before starting:
git stash
Development Loop
For each code change iteration, make a to do list for yourself and follow these steps:
- Write/modify code according to the user's requirements according to code generation instructions at .github/instructions/code_generation.instructions.md
- Test the code by writing test files according to testing instructions at .github/instructions/code_generation.instructions.md
- Verify functionality - ensure tests pass and code works as expected
- Stage and commit if tests pass:
git add -Agit commit -m "[descriptive message here]"- Use descriptive commit messages that explain what was added/changed and why
- Report status to user: what was changed, test results, commit hash
Error Handling
- If tests fail, do NOT commit
- Fix the issue and retry the loop
- If multiple attempts fail, ask user for guidance
- If git operations fail, report the error and ask for manual intervention
Session End
- Ask the user for explicit order to merge
#merge [commit message here]. If not received, do not merge. the user must provide a commit message in the mentioned format explicitly. - use the commit message provided by the user in the merge command.
- in the description of the commit message, add the branch name of the feature branch used like "Merged changes from branch [timestamp]" without the
LLM/prefix. - Before merging, show commit history:
git log --oneline - Execute merge:
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 First seen · 100 lines · 1,006 tokens per session scan A 47d39f191f90
daisyui code_generation_with_git.instructions.md is an instructions file published in the GitHub repository saadeghi/daisyui (42,615 stars, last pushed today), licensed MIT. It adds 1,006 tokens to every session, about $0.0040 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.