Borrowing it
Nothing to install: this file belongs to Lombiq/Tailwind-Agent-Skills. 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/Lombiq/Tailwind-Agent-Skills/dev/AGENTS.mdgit clone --depth 1 https://github.com/Lombiq/Tailwind-Agent-SkillsWrote 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/lombiq/tailwind-agent-skills/agents-md)<a href="https://agentmods.dev/instructions/lombiq/tailwind-agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/lombiq/tailwind-agent-skills/agents-md.svg" alt="Measured on agentmods" 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.00468 | $0.00468 |
| Opus 5 | $0.00234 | $0.00234 |
| Sonnet 5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
Tailwind-Agent-Skills AGENTS.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 8d 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.
What it actually says
Agent Guide
Purpose
This repo maintains an agent-friendly Tailwind CSS v4 docs workflow. The goal is to keep the skill current and easy to install in any agent without bundling the upstream docs.
Key paths
- Skill root:
skills/tailwind-4-docs/ - Docs snapshot (generated locally):
skills/tailwind-4-docs/references/docs/ - Docs index map (generated locally):
skills/tailwind-4-docs/references/docs-index.tsx - Snapshot metadata:
skills/tailwind-4-docs/references/docs-source.txt - Engineering playbook:
skills/tailwind-4-docs/references/engineering-playbook.md - Gotchas:
skills/tailwind-4-docs/references/gotchas.md - Sync script:
skills/tailwind-4-docs/scripts/sync_tailwind_docs.py
Update rules
- Do not hand-edit the MDX docs snapshot. Always refresh via the sync script.
- Do not commit the downloaded docs or docs index to the repo.
- Keep
docs-source.txtin sync with the snapshot commit (or the uninitialized placeholder). - Prefer minimal edits to
SKILL.md,references/engineering-playbook.md, andgotchas.mdwhen guidance changes. - Keep the skill framework-agnostic. Do not add Orchard Core, Razor, Liquid, or other product-specific concepts unless the skill is intentionally being specialized for that ecosystem.
- Use ASCII when editing unless the file already contains non-ASCII content.
Sync docs snapshot
Use the local clone if available (faster, deterministic):
python skills/tailwind-4-docs/scripts/sync_tailwind_docs.py --accept-docs-license --local-repo tmp-tailwindcss.com
If the local clone is missing, run without --local-repo to clone a temp copy.
Maintenance checklist
- Verify the snapshot commit updated in
docs-source.txt. - Scan docs for major v4 changes and update
gotchas.mdif needed. - Keep
references/engineering-playbook.mdaligned with the official docs structure and practical implementation guidance. - If you install the skill locally, restart or reload your agent to load it.
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.
- 8d ago First seen · 43 lines · 468 tokens per session scan A fddc5d3f4b9a
Tailwind-Agent-Skills AGENTS.md is an instructions file published in the GitHub repository Lombiq/Tailwind-Agent-Skills (69 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 468 tokens to every session, about $0.0023 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.