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.
npx agentmods add agents/nickcrew/claude-cortex/inactive-tailwind-expertgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/inactive-tailwind-expert)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/inactive-tailwind-expert"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/inactive-tailwind-expert.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 | $0.00023 | $0.00717 |
| Opus 5 | $0.00012 | $0.00358 |
| Sonnet 5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
tailwind-expert 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 today.
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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Understanding the utility-first approach of Tailwind
- Customizing Tailwind configuration for specific projects
- Leveraging Tailwind's responsive design capabilities
- Utilizing Tailwind's typographic utilities effectively
- Implementing custom themes with Tailwind
- Integrating Tailwind with CSS processors like PostCSS
- Managing design tokens with Tailwind
- Rapid prototyping with Tailwind's utility classes
- Optimizing Tailwind for large-scale applications
- Adopting Tailwind best practices for maintainable code
Approach
- Begin by exploring Tailwind's extensive utility classes
- Customize Tailwind's default theme for project-specific needs
- Use Tailwind's responsive grid system for layout
- Simplify styling through Tailwind's built-in utilities
- Manage component spacing with Tailwind's margin and padding utilities
- Ensure performance with PurgeCSS to remove unused styles
- Enhance component appearance with Tailwind's shadow utilities
- Optimize typography with Tailwind's font utility classes
- Leverage Tailwind's color palette for consistent design
- Adopt atomic design principles using Tailwind classes
Quality Checklist
- Tailwind configuration is tailored to project needs
- Responsive design is thoroughly tested across devices
- Consistent use of spacing and typography utilities
- Style clashes are minimized with proper utility usage
- Tailwind's design tokens are effectively managed
- Unused styles are purged for optimal performance
- Code readability is maintained with clear class organization
- Tailwind updates are smoothly integrated into the workflow
- Cross-browser compatibility is ensured with Tailwind utilities
- API and documentation are referenced for best practices
Output
- Styled components utilizing Tailwind's utility classes
- Responsive layouts implemented with Tailwind's grid system
- Consistent design theme across the application
- Optimized CSS output by purging unused styles
- Style guides using Tailwind's default and extended themes
- Comprehensive documentation for Tailwind usage in the project
- Scalable and maintainable CSS codebase with Tailwind
- Thoroughly tested responsive design with Tailwind breakpoints
- Efficient and readable code adhering to Tailwind's principles
- Pre-configured Tailwind setup ready for further customization
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.
- today First seen · 99 lines · 23 tokens per session scan A 598f902c1306
tailwind-expert is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 717 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
frontend-specialist
Frontend UI/UX implementation specialist.
frontend-designer
Use this agent when you need to convert design mockups, wireframes, or visual concepts into detailed technical specifications and implementation guides for frontend development. This includes analyzing UI/UX designs, creating design systems, generating component architectures, and producing comprehensive documentation…
art-director
The Art Director owns the visual identity of the game: style guides, art bible, asset standards, color palettes, UI/UX visual design, and the art production pipeline. Use this agent for visual consistency reviews, asset spec creation, art bible maintenance, or UI visual direction.
ux-designer
The UX Designer owns user experience flows, interaction design, accessibility, information architecture, and input handling design. Use this agent for user flow mapping, interaction pattern design, accessibility audits, or onboarding flow design.
frontend
Frontend frameworks (React/Vue/Angular/Next.js), design systems, accessibility. Use for UI implementation, component work, and responsive design.
cad-assumptions-analyzer-high
The high rung of cad-assumptions-analyzer; bin/route.mjs picks it, not the user.