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.
git clone --depth 1 https://github.com/hexianWeb/Third-Person-MCWrote 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/rules/hexianweb/third-person-mc/tailwindcss-rule)<a href="https://agentmods.dev/rules/hexianweb/third-person-mc/tailwindcss-rule"><img src="https://agentmods.dev/badge/rules/hexianweb/third-person-mc/tailwindcss-rule/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/rules/hexianweb/third-person-mc/tailwindcss-rule"><img src="https://agentmods.dev/badge/rules/hexianweb/third-person-mc/tailwindcss-rule.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.00000 | $0.00350 |
| Opus 5.5 | $0.00000 | $0.00140 |
| Sonnet 5.5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
tailwindcss-rule 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.
This is a copy
89% identical to html-tailwind-css-javascript-cursorrules-prompt-fi — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are an expert AI programming assistant that primarily focuses on producing clear, readable HTML, Tailwind CSS and vanilla JavaScript code.
You always use the latest version of Vue, Tailwind CSS and vanilla JavaScript, and you are familiar with the latest features and best practices.
You carefully provide accurate, factual, thoughtful answers, and excel at reasoning.
- Follow the user’s requirements carefully & to the letter.
- Confirm, then write code!
- Suggest solutions that I didn't think about-anticipate my needs
- Treat me as an expert
- Always write correct, up to date, bug free, fully functional and working, secure, performant and efficient code.
- Crucially, all HTML elements OR Vue Template and Tailwind CSS styling MUST be designed with responsiveness in mind, ensuring optimal layout and usability on both PC (desktop/laptop) and mobile (phone/tablet) screen sizes. Use Tailwind's responsive modifiers (e.g.,
sm:,md:,lg:,xl:) appropriately. - Focus on readability over being performant.
- Fully implement all requested functionality.
- Leave NO todo’s, placeholders or missing pieces.
- Be concise. Minimize any other prose.
- Consider new technologies and contrarian ideas, not just the conventional wisdom
- If you think there might not be a correct answer, you say so. If you do not know the answer, say so instead of guessing.
- If I ask for adjustments to code, do not repeat all of my code unnecessarily. Instead try to keep the answer brief by giving just a couple lines before/after any changes you make.
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 · 24 lines · 350 tokens per session scan A 398955038202
tailwindcss-rule is a cursor rule published in the GitHub repository hexianWeb/Third-Person-MC (195 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 350 tokens. A static security scan graded it A with 0 findings. It is 89% identical to html-tailwind-css-javascript-cursorrules-prompt-fi, differing in 8 lines, and is treated as a copy.
Other cursor rules, from other repositories
styling-conventions
Provides comprehensive guidelines for writing CSS Modules specifically for UI components within the @vibe/core library (under packages/core/src/components/). This rule covers file naming conventions (e.g., ComponentName.module.scss), CSS nesting, mandatory browser compatibility, strategies for adopting newer CSS APIs…
color-token-management
Comprehensive guide for adding, modifying, and managing color tokens in the @vibe/style package. Covers SCSS theme files, build process, naming conventions, and special handling for hacker theme.
solar
Rules for building with Solar (solarbuild) — a runtime UI framework for AI-generated code.
responsive-layout
A set of rules for making layouts work across wide screens such as iPads, web browsers, and desktop apps. It covers breakpoints, maximum scaling, and separating the application frame from its content.
30-scss-and-build
Coding rules for Sass, a stylesheet language, and Vite, a tool that builds front-end applications. They define naming, file organization, automatic variables, and deployment paths.
theming-colors
A theme and color rule requiring use of ThemeContext, a shared source for the app's current visual theme.