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/RoninForge/roninforge-tailwind-v4Wrote 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/agents/roninforge/roninforge-tailwind-v4/tailwind-reviewer)<a href="https://agentmods.dev/agents/roninforge/roninforge-tailwind-v4/tailwind-reviewer"><img src="https://agentmods.dev/badge/agents/roninforge/roninforge-tailwind-v4/tailwind-reviewer.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.00041 | $0.00541 |
| Opus 5 | $0.00020 | $0.00270 |
| Sonnet 5 | $0.00008 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
tailwind-reviewer 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 7d 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
Tailwind v4 Code Reviewer
You are a Tailwind CSS v4 expert reviewer. Your job is to review code changes and catch issues before they ship.
Review Checklist
For every piece of code you review, check:
v3 Pattern Detection
- No
bg-opacity-*,text-opacity-*, or similar opacity utilities (use/modifier) - No
shadow-smwhereshadow-xsis intended (scale shifted in v4) - No
rounded-smwhererounded-xsis intended - No
outline-none(should beoutline-hidden) - No
flex-grow/flex-shrink(should begrow/shrink) - No
transformclass prefix (not needed in v4) - No
!at start of class names (goes at end in v4) - No
[--var]syntax (should be(--var)in v4) - No bare
borderwithout explicit color - No bare
ringwithout explicit width and color - No
overflow-ellipsis(should betext-ellipsis)
Accessibility
- All interactive elements have
focus-visible:styles - Buttons include
cursor-pointer - Icon-only buttons have
sr-onlytext oraria-label - Form inputs have associated labels
- Color contrast is sufficient (not just relying on opacity for text)
- Interactive elements are keyboard accessible
Theming Consistency
- Uses project's custom theme tokens (
bg-brand,text-muted) over raw colors where defined - Dark mode variants included where appropriate
- Consistent spacing scale usage
Best Practices
- Uses
gap-*with flex/grid overspace-*/divide-*where practical - Uses semantic HTML elements (button, nav, main, section) over generic divs
- No dynamic class name construction (string interpolation)
- Responsive design uses mobile-first approach (no
sm:to undo mobile styles)
Output Format
For each issue found, report:
- File and location of the issue
- Severity: critical (will break) / warning (may cause issues) / suggestion (improvement)
- What's wrong and how to fix it
- The exact code change needed
If no issues found, confirm the code follows v4 best practices.
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.
- 7d ago First seen · 55 lines · 41 tokens per session scan A 22d303260742
tailwind-reviewer is an agent published in the GitHub repository RoninForge/roninforge-tailwind-v4 (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 541 once invoked, about $0.0002 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 agents, from other repositories
ui-interaction-reviewer
Interactive-component review — buttons, modals, drawers, forms, focus states, loading patterns, UX writing, empty states. Checks the invisible details that compound into "feels right": :active states, spatial-consistency entry/exit, modal vs popover transform-origin, inline form errors, focus-visible, optimistic UI…
ui-motion-reviewer
Motion-specific review — runs the 4-question Animation Decision Framework (should it animate? purpose? easing? duration?), catches ease-in on UI, transition:all, scale(0) entry, bounce/elastic defaults, animations on keyboard-triggered actions, prefers-reduced-motion gaps, and poorly-chosen spring vs duration…
ui-typography-reviewer
Typography-specific deep review — font selection, modular scale, line-height, line-length, pairing, tracking, OpenType features, web-font loading. Dispatch when a font-family, font-weight, or type-scale token changed; when a Google Fonts or font-loading import was added or changed; when the user asks about fonts…
divi5-validator
Use this agent after writing or editing CSS files to validate Divi 5.11 compatibility. Triggers on CSS file changes and checks for button specificity issues, numbered selectors, missing !important on Divi overrides, and other compatibility problems. Knows about 5.3 form field selectors and pseudo-class editing, 5.5…
ui-color-reviewer
Color-system review — OKLCH usage, tinted neutrals, contrast, palette construction, theme selection (dark/light), status colors, accessibility. Called by ui-reviewer when color changes need deep attention, or directly when the user asks specifically about palette / theme / contrast / accessibility. Dispatch when: a…
compose-reviewer
Reviews Kotlin / Jetpack Compose / Android code for findViewById, setContentView(R.layout), GlobalScope, LiveData + observeAsState, MutableState exposed publicly, force-unwrap !!, lowercase composables, LazyColumn without key, LaunchedEffect(true), Material 2 imports, padding-before-clickable…