Borrowing it
Nothing to install: this file belongs to clarity-contrib/tailwindcss-mcp-server. 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/clarity-contrib/tailwindcss-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/clarity-contrib/tailwindcss-mcp-serverWrote 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/clarity-contrib/tailwindcss-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/clarity-contrib/tailwindcss-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/clarity-contrib/tailwindcss-mcp-server/claude-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.00856 | $0.00856 |
| Opus 5 | $0.00428 | $0.00428 |
| Sonnet 5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
tailwindcss-mcp-server CLAUDE.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 6d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a TypeScript-based MCP (Model Context Protocol) server for TailwindCSS, providing comprehensive tools for AI agents to understand and work with the TailwindCSS utility-first framework. The server offers both informational tools (documentation, utilities, configuration) and action tools (installation, CSS conversion, component generation).
Development Commands
Build & Development
bun install- Install dependenciesbun run build- Build TypeScript to JavaScript and set executable permissionsbun run watch- Watch mode for development (auto-rebuilds on file changes)
Testing & Debugging
bun run testorbunx vitest run- Run all testsbun run inspector- Launch MCP Inspector for debugging the server through a web interface
Publishing
bun publish- Publish to npm (auto-builds viapreparescript)- Always use
bunfor all package management — never npm/yarn/pnpm - Important: When any new files/directories are added under
src/, make surebuild/<dir>is listed in thefilesarray inpackage.json— otherwise the published package will be broken
Manual MCP Integration Testing
After making changes, always verify the package works end-to-end as an MCP server:
- Build:
bun run build - Run the sibling test project:
bun run ../test-tailwindcss-mcp/index.ts— this spawns the MCP server viabunx, connects as a client, and calls multiple tools with v3/v4 params - Or use the MCP Inspector:
bun run inspector— opens a web UI to call tools interactively - Verify version-specific outputs differ: v3
module.exportsvs v4@theme, v3tailwind.config.jsvs v4 none, etc. - stderr logs (e.g.
[v4] Scraping documentation page: ...) confirm which version/URL is being hit
Architecture & Key Components
Project Goals
- Primary: Enable AI agents to provide accurate TailwindCSS guidance by accessing comprehensive documentation, utility classes, and configuration patterns
- Secondary: Execute practical actions like installing TailwindCSS, converting CSS to utilities, generating color palettes, and creating component templates
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.
- 6d ago First seen · 72 lines · 856 tokens per session scan A 5576cfd50ceb
tailwindcss-mcp-server CLAUDE.md is an instructions file published in the GitHub repository clarity-contrib/tailwindcss-mcp-server (1 stars, last pushed 6mo ago), licensed MIT. It adds 856 tokens to every session, about $0.0043 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-31.
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.