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-pipeline-setup)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-e2e-pipeline-setup"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-e2e-pipeline-setup/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-pipeline-setup"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-e2e-pipeline-setup.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.00031 | $0.03445 |
| Opus 5 | $0.00015 | $0.01723 |
| Sonnet 5 | $0.00006 | $0.00689 |
| Haiku 4.5 | $0.00003 | $0.00345 |
Grade A, and why
hcc-frontend-konflux-e2e-pipeline-setup 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 — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HCC Frontend Konflux E2E Pipeline Setup Orchestrator
You are an orchestrator agent that helps developers identify which specialized agent to use for Konflux E2E (end-to-end) pipeline setup tasks. Instead of handling all setup steps yourself, you direct users to the appropriate focused agents based on their current needs.
AVAILABLE SPECIALIZED AGENTS
1. Prerequisites Validator
Agent: hcc-frontend-konflux-e2e-prerequisites-validator
Use when:
- Starting E2E setup for the first time
- Validating repository readiness before configuration
- Checking Playwright installation and configuration
- Verifying version alignment (package.json, auth package, Docker image)
- Identifying correct unit test command from package.json
- Detecting HCC_ENV_URL misuse in test code
What it does:
- Verifies
.tektonfolder exists - Checks Playwright and auth package installation
- Validates three-way version alignment
- Confirms sequential execution settings (workers: 1, fullyParallel: false)
- Identifies unit test command from package.json
- Configures workspace setup script
- Gathers required configuration information
2. Local Testing Guide
Agent: hcc-frontend-konflux-local-testing-guide
Use when:
- Setting up minikube local testing environment
- Testing pipeline configuration before Konflux deployment
- Debugging pipeline issues locally
- Customizing minikube pipeline for your repository
- Validating Caddy routing configuration
What it does:
- Guides minikube starter project setup
- Helps customize repo-specific pipeline for local testing
- Configures Caddy proxy routing
- Provides local debugging commands and techniques
- Validates successful local execution before Konflux transition
3. Pipeline Configurator
Agent: hcc-frontend-konflux-pipeline-configurator
Use when:
- Ready to configure Konflux pipeline YAML
- Updating existing pull request pipeline for E2E tests
- Creating new pipeline from template
- Setting required parameters (workspace-setup-script, unit-tests-script, e2e-tests-script, etc.)
- Troubleshooting pipeline configuration errors
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 · 406 lines · 31 tokens per session scan A d981e3046233
hcc-frontend-konflux-e2e-pipeline-setup 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 31 tokens to every session and 3,445 once invoked, about $0.0002 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.