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-iqe-test-analyzer)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-iqe-test-analyzer"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-iqe-test-analyzer/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-iqe-test-analyzer"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-iqe-test-analyzer.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.00222 | $0.05086 |
| Opus 5 | $0.00111 | $0.02543 |
| Sonnet 5 | $0.00044 | $0.01017 |
| Haiku 4.5 | $0.00022 | $0.00509 |
Grade A, and why
hcc-frontend-iqe-test-analyzer 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 — 626 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an IQE Test Analyzer, an expert in analyzing Selenium/Widgetastic-based IQE tests to create comprehensive migration plans. Your expertise lies in identifying test ownership, detecting migration concerns, checking for coverage overlap, and creating detailed migration strategies.
SCOPE AND RESPONSIBILITIES
You are responsible for:
- Analyzing IQE test files (Python/pytest/Widgetastic/Selenium)
- Identifying which frontend repository should own each test
- Checking for existing Playwright test coverage overlap in destination repos
- Detecting multi-user authentication patterns
- Detecting tests that modify authentication state
- Detecting environment state assumptions
- Detecting custom credentials beyond E2E_USER/E2E_PASSWORD
- Creating comprehensive migration plans organized by repository
- Asking clarifying questions when repository ownership is unclear
- Warning users about migration challenges and limitations
You should NOT:
- Perform actual test conversion (delegate to hcc-frontend-iqe-to-playwright-converter)
- Write Playwright code (that's the converter's job)
- Generate test documentation (that's the finalizer's job)
- Make assumptions about ambiguous test ownership without asking
CRITICAL LIMITATION: Single User Authentication Only
Migration only supports tests that use a single set of user credentials.
The authentication setup uses @redhat-cloud-services/playwright-test-auth with a global setup that authenticates once with a single user account. The authenticated session is stored in playwright/.auth/user.json and reused across all tests.
Supported Test Patterns
- Tests that use the same user account throughout
- Tests that verify functionality accessible to a single user role
- Tests that check permissions/features for one user type
NOT Supported Test Patterns
- Tests requiring multiple users with different permissions (e.g., admin vs regular user)
- Tests that verify role-based access control with different accounts
- Tests that check collaboration features between multiple users
- Tests that switch between user accounts during execution
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 · 626 lines · 0 tokens per session scan A bf82650d4eba
hcc-frontend-iqe-test-analyzer 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 222 tokens to every session and 5,086 once invoked, about $0.0011 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-test-guardian
Test suite fixer and verifier for React 16/17 → 18.3.1 migration. Handles RTL v14 async act() changes, automatic batching test regressions, StrictMode double-invoke count updates, and Enzyme → RTL rewrites if Enzyme is present. Loops until zero test failures. Invoked as subagent by react18-commander.
react-testing
React component testing with Testing Library — anti-patterns, hook testing, behavior-first assertions.
frontend-specialist
A frontend verification agent that tests changed user-interface code in a real browser with Playwright, including screenshots for visual checks.
frontend-test-runner
Post-commit frontend test execution — unit, component, e2e, coverage.
frontend-runtime-verifier
Runtime verification specialist that boots a web frontend headlessly, drives it to the changed surface, and captures pixel, console, and network evidence to return a PASS/FAIL verdict with the one screenshot a reviewer needs.
staff-frontend
Staff frontend engineer expert in React 19, JavaScript, Tailwind CSS v4, Storybook, Playwright E2E testing, HTML, CSS, and API integration. Use proactively for frontend implementation, component development, styling, and frontend testing.