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/jrmybtlr/useclassyWrote 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/jrmybtlr/useclassy/useclassy-setup.cursor-rule)<a href="https://agentmods.dev/rules/jrmybtlr/useclassy/useclassy-setup.cursor-rule"><img src="https://agentmods.dev/badge/rules/jrmybtlr/useclassy/useclassy-setup.cursor-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/jrmybtlr/useclassy/useclassy-setup.cursor-rule"><img src="https://agentmods.dev/badge/rules/jrmybtlr/useclassy/useclassy-setup.cursor-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.00501 |
| Opus 5.5 | $0.00000 | $0.00200 |
| Sonnet 5.5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
useclassy-setup.cursor-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.
What it actually says
When adding or fixing UseClassy in this project:
- Install
vite-plugin-useclassyas a dev dependency (use this repo’s package manager). - In
vite.config.*, importuseClassyfromvite-plugin-useclassyand adduseClassy({ language: 'vue' | 'react' | 'blade' | 'svelte' })topluginsbefore@tailwindcss/viteor other CSS plugins. For Svelte, also place it before@sveltejs/vite-plugin-svelte. - Tailwind v4 (CSS uses
@import "tailwindcss"): In that stylesheet, add an@sourceline pointing at the generated manifest. Default manifest path is.classy/output.classy.htmlfrom the project root; the@sourcepath must be relative to the CSS file. In JavaScript configs you can compute the line withgetUseClassyTailwindSourceDirective(cssAbsolutePath, projectRoot)fromvite-plugin-useclassy. - Tailwind v3: Add
./.classy/output.classy.htmltocontentintailwind.config.*(or usegetUseClassyTailwindV3ContentEntry()from the package for the default path). - VS Code (Tailwind only): Merge
tailwindCSS.classAttributesto includeclass:[\\w:/@\\[\\]\\-=&*>.]*and, for React,className:[\\w:/@\\[\\]\\-=&*>.]*. Skip this for UnoCSS — use the UnoCSS extension. - Run dev once so
.classy/output.classy.htmlis generated.
Prefer npx vite-plugin-useclassy init (after installing the package) instead of hand-editing when possible. init installs the UseClassy authoring skill (.agents/skills), these Cursor rules, and an AGENTS.md section by default. Pass --no-skills to skip agent files. Add --with-claude if you also use Claude Code.
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 Changed 76705838c96f
- 1mo ago First seen · 16 lines · 0 tokens per session scan A 26d34c800f01
useclassy-setup.cursor-rule is a cursor rule published in the GitHub repository jrmybtlr/useclassy (28 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 501 tokens. 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
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
z-index
Z-index layering conventions for consistent stacking.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.