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 rules/agentset-ai/agentset/tailwindgit clone --depth 1 https://github.com/agentset-ai/agentsetWhat 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.02753 | $0.02753 |
| Opus 5 | $0.01376 | $0.01376 |
| Sonnet 5 | $0.00551 | $0.00551 |
| Haiku 4.5 | $0.00275 | $0.00275 |
Grade A, and why
tailwindcss 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.
How it starts
The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailwind CSS Rules and Best Practices
Core Principles
- Always use Tailwind CSS v4.1+ - Ensure the codebase is using the latest version
- Do not use deprecated or removed utilities - ALWAYS use the replacement
- Never use
@apply- Use CSS variables, the--spacing()function, or framework components instead - Check for redundant classes - Remove any classes that aren't necessary
- Group elements logically to simplify responsive tweaks later
Upgrading to Tailwind CSS v4
Before Upgrading
- Always read the upgrade documentation first - Read https://tailwindcss.com/docs/upgrade-guide and https://tailwindcss.com/blog/tailwindcss-v4 before starting an upgrade.
- Ensure the git repository is in a clean state before starting
Upgrade Process
- Run the upgrade command:
npx @tailwindcss/upgrade@latestfor both major and minor updates - The tool will convert JavaScript config files to the new CSS format
- Review all changes extensively to clean up any false positives
- Test thoroughly across your application
Breaking Changes Reference
Removed Utilities (NEVER use these in v4)
| ❌ Deprecated | ✅ Replacement |
|---|---|
bg-opacity-* |
Use opacity modifiers like bg-black/50 |
text-opacity-* |
Use opacity modifiers like text-black/50 |
border-opacity-* |
Use opacity modifiers like border-black/50 |
divide-opacity-* |
Use opacity modifiers like divide-black/50 |
ring-opacity-* |
Use opacity modifiers like ring-black/50 |
placeholder-opacity-* |
Use opacity modifiers like placeholder-black/50 |
flex-shrink-* |
shrink-* |
flex-grow-* |
grow-* |
overflow-ellipsis |
text-ellipsis |
decoration-slice |
box-decoration-slice |
decoration-clone |
box-decoration-clone |
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 · 372 lines · 2,753 tokens per session scan A ededbd5ba068
tailwindcss is a cursor rule published in the GitHub repository agentset-ai/agentset (2,076 stars, last pushed 1mo ago), licensed MIT. It adds 2,753 tokens to every session, about $0.0138 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 cursor rules, from other repositories
project-rules
智能体平台前端项目开发规则和最佳实践.
cursorrules
所有 Git 提交说明必须使用简体中文书写，禁止使用英文标题或英文正文。 专有名词、包名、API 路径等技术标识可保留英文。.
write-migration
Author an idempotent, state-detecting migration under scripts/migrations/ for a breaking llm-wiki-memory change. Use when shipping a breaking change to the engine, or when asked to write a migration / upgrade path. Replaces the retired release-runbook flow.
debug-capture-pipeline
Debug llm-wiki-memory capture/recall — flush breadcrumbs, daily-vs-compile lag, failed-distill stash recovery, embedding cache, hook wiring. Use when memory didn't capture, doesn't recall, or a hook/cron looks broken.
self-observability
Self-observability (watch llm-wiki-memory while you work; offer fixes) — This rule applies to every AI agent (Claude Code, Cursor, Codex, generic MCP clients) working Canonical file is .agents/rules/self-observability.md.
vios-sqa
VIOS SQA agent. One-click build → deploy → test → UI validation cycle. Use when asked to run regression tests, check test results, deploy for testing, or verify UI behavior.