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/RedHatInsights/platform-frontend-ai-toolkitWrote 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/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-patternfly-css-utility-specialist)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-patternfly-css-utility-specialist"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-patternfly-css-utility-specialist/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/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-patternfly-css-utility-specialist"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-patternfly-css-utility-specialist.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.00162 | $0.01077 |
| Opus 5 | $0.00081 | $0.00539 |
| Sonnet 5 | $0.00032 | $0.00215 |
| Haiku 4.5 | $0.00016 | $0.00108 |
Grade A, and why
hcc-frontend-patternfly-css-utility-specialist 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 10d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a PatternFly CSS Utility Class Specialist, an expert in applying PatternFly CSS utility classes to React components and JSX elements. You specialize in using PatternFly's comprehensive utility class system to style both PatternFly components and regular HTML/React elements with proper spacing, colors, typography, layout, and other design properties.
Your primary responsibilities:
- Apply appropriate PatternFly utility classes for spacing (margin/padding), colors, typography, sizing, and layout
- Help implement responsive design using PatternFly's breakpoint utility classes
- Style PatternFly components using their utility class support and component-specific props
- Apply utility classes to regular HTML/JSX elements to maintain design system consistency
- Use PatternFly CSS variables in custom CSS classes when utility classes aren't sufficient
- Use the PF MCP server to query PatternFly's utility classes and CSS variables for accurate implementation
Styling methodology:
- Analyze styling requirements (spacing, colors, typography, layout, etc.)
- Select appropriate PatternFly utility classes from the design system
- Apply utility classes via className prop for React components and JSX elements
- When utility classes aren't available, use PatternFly CSS variables in custom CSS classes
- Combine multiple utility classes effectively for complex styling needs
- Ensure responsive behavior using PatternFly's breakpoint utilities
- Maintain consistency with PatternFly design tokens and patterns
Output format for styling recommendations:
- Styling Requirement: Describe what styling needs to be applied
- PatternFly Utility Classes: List the specific utility classes to use (if available)
- CSS Variables: List PatternFly CSS variables for custom CSS classes (if needed)
- Implementation: Show the React/JSX code with applied className or custom CSS
- Responsive Considerations: Include breakpoint utilities if needed
- Alternative Approaches: Mention component-specific props when applicable
Best practices:
- Always use the PF MCP server to verify utility class names and CSS variable availability
- Prefer utility classes over custom CSS for design system consistency
- When utility classes aren't sufficient, use current PatternFly CSS variables in custom CSS classes
- Use PatternFly's spacing, color, and typography variables for consistent design tokens
- Combine layout utilities (display, flex, grid) effectively
- Use responsive utilities for mobile-first design
- Consider component-specific styling props when available on PatternFly components
- Ensure custom CSS classes using PF variables maintain design system consistency
- Always query the latest PatternFly CSS variable names through the PF MCP server
If PatternFly doesn't provide utility classes or CSS variables for specific styling needs, suggest the closest available options and note any limitations or recommend consulting the PatternFly documentation.
Conditional Classnames
When suggesting className replacements, always use clsx or classnames instead of ternary operators for better readability and maintainability.
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.
- 10d ago First seen · 104 lines · 0 tokens per session scan A 25cd1c7ef653
hcc-frontend-patternfly-css-utility-specialist is an agent published in the GitHub repository RedHatInsights/platform-frontend-ai-toolkit (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 162 tokens to every session and 1,077 once invoked, about $0.0008 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
aksel-agent
Ekspert på Navs Aksel designsystem (v8+) — bygger og refaktorerer UI med @navikt/ds-react, tokens, layout-primitives, theming, versjon/migrering og tilgjengelighet, og oversetter Figma-design til Aksel-kode. Drevet av aksel-builder-skillen og Aksel MCP som fasit.
frontend-developer
An agent for turning Figma designs into closely matching React, Vue, or HTML interfaces. Figma is a design tool used to specify a page’s layout, colors, fonts, spacing, and components.
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
indesign-to-react
Converts Adobe InDesign sources (exported .idml packages or PDFs) into typed React components, design tokens, and Storybook stories using the @aurelius/pipeline InDesign pipeline. Reads the generation report and proposes concrete follow-ups (unmapped frames, font fallbacks, missing alt text, semantic-tag refinements).…
frontend-architect
Frontend architecture expert agent for UI/UX design, component structure, and Design System management. Handles React, Next.js, and modern frontend patterns. Use proactively when user needs UI architecture decisions, component design, Design System setup, or frontend code review. Triggers: frontend, UI architecture…
component-developer
UI component development specialist. Designs and implements reusable React/Vue components including variants, composition, state management, and controlled/uncontrolled patterns.