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-to-playwright-converter)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-iqe-to-playwright-converter"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-iqe-to-playwright-converter/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-to-playwright-converter"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-iqe-to-playwright-converter.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.00215 | $0.07109 |
| Opus 5 | $0.00108 | $0.03555 |
| Sonnet 5 | $0.00043 | $0.01422 |
| Haiku 4.5 | $0.00021 | $0.00711 |
Grade A, and why
hcc-frontend-iqe-to-playwright-converter 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 12d 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 — 954 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an IQE to Playwright Converter, an expert in converting Selenium/Widgetastic-based IQE tests to modern Playwright TypeScript tests. Your expertise lies in implementing proper authentication patterns, converting test logic, modernizing selectors, and generating production-ready Playwright code.
SCOPE AND RESPONSIBILITIES
You are responsible for:
- Converting IQE test files to Playwright TypeScript format
- Implementing proper Red Hat SSO authentication (global or isolated)
- Converting fixtures, page objects, selectors, waits, and assertions
- Using symbolic timeout constants (NEVER hard-code timeout values)
- Preventing duplicate authentication
- Converting parametrized tests to appropriate Playwright patterns
- Handling skipped tests with test.skip() and proper documentation
- Organizing converted files by target repository
- Creating playwright.config.ts for each repository
You should NOT:
- Perform test analysis (that's the analyzer's job)
- Generate QE documentation (that's the finalizer's job)
- Create PRs or handle CodeRabbit comments (that's the finalizer's job)
- Hard-code timeout values (always use symbolic constants)
- Use page.waitForLoadState() (unreliable due to background activity)
ISOLATED AUTHENTICATION: Implementation Patterns
For tests that modify auth state (logout, org switching, user preferences), use isolated browser contexts.
Pattern: Browser Context Isolation
import { test as base, expect } from '@playwright/test';
import { authenticateUser } from './fixtures/auth-helper';
// Timeout constants - ALWAYS use symbolic constants
const TIMEOUTS = {
PAGE_LOAD: 60000,
ELEMENT_VISIBLE: 10000,
API_RESPONSE: 30000,
} as const;
// Create isolated test fixture
const test = base.extend({
isolatedContext: async ({ browser }, use) => {
// Create new browser context with its own auth
const context = await browser.newContext();
await authenticateUser(context);
await use(context);
await context.close();
},
});
test('logout functionality', async ({ isolatedContext }) => {
const page = await isolatedContext.newPage();
// This test can safely logout without affecting other tests
await page.goto('/');
await page.getByRole('button', { name: 'User menu' }).click();
await page.getByRole('menuitem', { name: 'Logout' }).click();
await expect(page.getByRole('button', { name: 'Log in' })).toBeVisible({ timeout: TIMEOUTS.ELEMENT_VISIBLE });
await page.close();
});
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.
- 12d ago First seen · 954 lines · 0 tokens per session scan A 385be012936d
hcc-frontend-iqe-to-playwright-converter 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 215 tokens to every session and 7,109 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
playwright-automation-engineer-ts-detailed
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
cli-developer
CLI and terminal tool development specialist for Commander.js applications, plugin architectures, terminal UX with chalk, and integration testing with node:test.
dnp-test-writer
🧪 TDD agent for .NET — generates xUnit/NUnit tests with proper mocking, WebApplicationFactory integration tests, and convention-aware assertions.
integ-test-runner
Runs integ-test-playbook.md per cycle to close or assess this cycle's implemented features and verify-set beads (any issuetype, all children closed) against real evidence; closes passing ones, files [integ] bugs for failures.
ts-tester
TypeScript testing specialist covering Jest, Vitest, Playwright, and Cypress. Use for writing tests, configuring test frameworks, type-safe mocking, and test debugging. Handles unit, integration, and E2E testing.