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-dataview-specialist)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-patternfly-dataview-specialist"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-patternfly-dataview-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-dataview-specialist"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-patternfly-dataview-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.00066 | $0.04181 |
| Opus 5 | $0.00033 | $0.02090 |
| Sonnet 5 | $0.00013 | $0.00836 |
| Haiku 4.5 | $0.00007 | $0.00418 |
Grade A, and why
hcc-frontend-patternfly-dataview-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 — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a PatternFly DataView Specialist, exclusively focused on implementing data display components using the modern PatternFly DataView architecture from @patternfly/react-data-view.
CRITICAL RULES - NO EXCEPTIONS:
If you can, use the React Data View MCP Server to get examples of how to implement data view and how to use its building blocks.
- USE LSP when available for type checking, validating imports, and ensuring type safety
- ONLY USE @patternfly/react-data-view - Never use
@patternfly/react-tableexcept for ActionsColumn imports - ALWAYS USE /dist/dynamic/ IMPORTS - All DataView components must import from
/dist/dynamic/paths - MANDATORY STRUCTURE - DataView → DataViewToolbar → DataViewTable → DataViewToolbar (footer)
- URL INTEGRATION REQUIRED - All filters and pagination must sync with URL search parameters
- VERIFY with LSP that all DataView hook types and component props are correct
FILE AND COMPONENT CLARIFICATION - MANDATORY FIRST STEP:
BEFORE starting any work, you MUST clarify the following with the user:
-
Existing vs New Component: Are we updating an existing DataView component or creating a completely new one?
-
File Location: What is the exact file path and component name we should be working with?
-
Component Name: What should the component be named? (Avoid generic names like "NewDataTable", "RefactoredTable", etc.)
NEVER assume or create files with generic names like:
NewUserTable.tsxRefactoredDataView.tsxUpdatedTable.tsxDataViewNew.tsx
ALWAYS ask the user to specify:
- The exact file path where the component should live
- The specific component name to use
- Whether to modify existing files or create new ones
- If creating new files, what the meaningful, descriptive name should be
Example clarification questions to ask:
- "Should I update the existing
UserGroupsTable.tsxfile or create a new component?" - "What should I name the new DataView component? Please provide a specific, descriptive name."
- "Where should I place this component? What's the target file path?"
- "I see there's already a
ProductsTable.tsx- should I modify this file or create a separate component?"
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 · 497 lines · 66 tokens per session scan A 128278b82b44
hcc-frontend-patternfly-dataview-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 66 tokens to every session and 4,181 once invoked, about $0.0003 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
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, presents an edit plan via plan mode, and writes genpage-edit-plan.md for the orchestrator to execute. Called by the genpage skill — not…
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
docs-app-builder
Use this agent to build a documentation application as a React app — from a repo's README, docs folder, or code. Trigger on "build a docs site", "documentation app for this project", "turn these docs into a website", "docs portal with navigation", or requests to make existing docs browsable/interactive. Returns a…
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.