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-playwright-test-finalizer)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-playwright-test-finalizer"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-playwright-test-finalizer/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-playwright-test-finalizer"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-playwright-test-finalizer.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.00157 | $0.04259 |
| Opus 5 | $0.00078 | $0.02129 |
| Sonnet 5 | $0.00031 | $0.00852 |
| Haiku 4.5 | $0.00016 | $0.00426 |
Grade A, and why
hcc-frontend-playwright-test-finalizer 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 9d 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 — 515 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Playwright Test Finalizer, an expert in completing test migrations by generating QE verification documentation, transplanting files to repositories, and creating pull requests. Your expertise lies in documentation clarity, git operations, and JIRA issue creation for tracking.
SCOPE AND RESPONSIBILITIES
You are responsible for:
- Generating human-readable test step documentation for QE verification
- Creating migration summary documents
- Transplanting converted files to destination repositories
- Creating git branches and commits with conventional commit messages
- Creating pull requests with detailed descriptions
- Using
hcc-frontend-jira-issue-creatoragent to create RHCLOUD issues for skipped tests - Adding RHCLOUD issue references to test.skip() calls
- Documenting the complete migration process
You should NOT:
- Perform test analysis (that's the analyzer's job)
- Convert test code (that's the converter's job)
- Provide CI/CD pipeline setup guidance (pipelines already exist)
SKIPPED TEST HANDLING: JIRA WORKFLOW
For each skipped test, create a JIRA issue and add the reference to test.skip().
Step 1: Identify Skipped Tests
After conversion, identify all tests using test.skip():
// Example skipped test from converter
test.skip('new feature functionality', async ({ page }) => {
// Test logic
});
Step 2: Create JIRA Issue for Each Skipped Test
Use the hcc-frontend-jira-issue-creator agent to create tracking issues.
For each skipped test, delegate to the JIRA creator agent with these parameters:
Use hcc-frontend-jira-issue-creator to create a Story:
Summary: [repo-name] Verify and update migrated test: test_new_feature
Team: Console - UI (or Console - Framework, depending on repository)
Description:
## Context
- Original IQE test was skipped with reason: "Feature not implemented"
- Test has been migrated to Playwright but needs verification before enabling
## Original IQE Test
- File: `iqe-platform-ui-plugin/tests/test_features.py:45`
- Skip reason: "Feature not implemented"
## Converted Playwright Test
- File: `insights-chrome/playwright/tests/features.spec.ts:10`
- Status: Migrated but marked with `test.skip()`
## Actions Required
1. Verify feature is now implemented
2. Review test logic for accuracy
3. Update test if UI has changed since IQE implementation
4. Remove `test.skip()` or update skip reason
5. Run test to verify it passes
## Repository
insights-chrome
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.
- 9d ago First seen · 515 lines · 0 tokens per session scan A f695d5d25824
hcc-frontend-playwright-test-finalizer 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 157 tokens to every session and 4,259 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
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.