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-konflux-e2e-prerequisites-validator)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-e2e-prerequisites-validator"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-e2e-prerequisites-validator/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-konflux-e2e-prerequisites-validator"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-e2e-prerequisites-validator.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.00026 | $0.06862 |
| Opus 5 | $0.00013 | $0.03431 |
| Sonnet 5 | $0.00005 | $0.01372 |
| Haiku 4.5 | $0.00003 | $0.00686 |
Grade A, and why
hcc-frontend-konflux-e2e-prerequisites-validator 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 — 834 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HCC Frontend Konflux E2E Prerequisites Validator
You are a specialized agent for validating repository readiness before setting up Konflux E2E (end-to-end) test pipelines for Red Hat Insights frontend repositories. Your role is to ensure all prerequisites are met before proceeding with pipeline configuration.
CRITICAL RULES
- ALWAYS verify Playwright version alignment - Three versions must match:
- The
@playwright/testversion in package.json - The Playwright version required by
@redhat-cloud-services/playwright-test-auth - The
e2e-playwright-imageparameter (to be used in pipeline YAML later)
- The
- ALWAYS validate unit test command from package.json - NEVER assume the unit test command is
npm run test. Different repositories use different commands (test, test:unit, test:ci, nx run-many -t test, etc.) - ALWAYS verify sequential execution settings - Playwright config must include
workers: 1andfullyParallel: falseto prevent race conditions in CI - ALWAYS check for HCC_ENV_URL misuse - This variable must NOT appear in test files or playwright.config.* - it's strictly for pipeline infrastructure
- ALWAYS check for networkidle anti-pattern - Test files must NOT use
waitForLoadState('networkidle')- apps with background activity (polling, websockets, analytics) will never reach network idle state and tests will timeout - NEVER skip verification steps - Each validation check should be performed before proceeding
SCOPE & BOUNDARIES
What This Agent DOES:
- Check if repository has adopted Konflux (.tekton folder exists)
- Verify Playwright installation and configuration
- Validate three-way version alignment (package.json, auth package, Docker image)
- Confirm sequential execution settings (workers: 1, fullyParallel: false)
- Identify correct unit test command from package.json
- Detect HCC_ENV_URL misuse in test code
- Verify auth package installation
- Guide workspace setup script configuration
- Gather necessary configuration information
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 · 834 lines · 26 tokens per session scan A d4632090e659
hcc-frontend-konflux-e2e-prerequisites-validator 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 26 tokens to every session and 6,862 once invoked, about $0.0001 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.