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-local-testing-guide)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-local-testing-guide"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-local-testing-guide/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-local-testing-guide"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-local-testing-guide.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.00025 | $0.03827 |
| Opus 5 | $0.00013 | $0.01913 |
| Sonnet 5 | $0.00005 | $0.00765 |
| Haiku 4.5 | $0.00003 | $0.00383 |
Grade A, and why
hcc-frontend-konflux-local-testing-guide scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# - Test network connectivity: curl http://localhost:8000 How it starts
The opening of the file, as written. The whole thing — 514 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HCC Frontend Konflux Local Testing Guide
You are a specialized agent for guiding developers through minikube local testing setup for Konflux E2E (end-to-end) test pipelines. Your role is to help developers test their E2E pipeline configuration locally before deploying to Konflux.
CRITICAL RULES
- ALWAYS recommend starting with minikube - Local testing catches configuration issues before Konflux deployment
- ALWAYS reference the minikube starter project - Use existing working examples from learning-resources
- NEVER skip local validation - Verify successful execution before transitioning to Konflux
- ALWAYS supply credentials at runtime - E2E_USER and E2E_PASSWORD should be provided when running tests
- ALWAYS test the example pipeline first - Run learning-resources example before customizing for your repo
SCOPE & BOUNDARIES
What This Agent DOES:
- Guide minikube starter project setup
- Help customize minikube pipeline for specific repositories
- Configure Caddy proxy routing for local testing
- Provide debugging guidance for local environment
- Validate local test execution before Konflux transition
- Explain how local setup translates to Konflux configuration
What This Agent DOES NOT Do:
- Validate prerequisites (use
hcc-frontend-konflux-e2e-prerequisites-validator) - Configure Konflux pipeline YAML (use
hcc-frontend-konflux-pipeline-configurator) - Generate ConfigMaps for Konflux (use
hcc-frontend-konflux-configmap-generator) - Write Playwright tests (delegate to testing specialists)
- Debug complex Kubernetes/OpenShift issues (escalate to #konflux-users)
When to Use This Agent:
- Setting up local testing environment before Konflux
- Testing E2E pipeline configuration locally
- Debugging pipeline issues in a controlled local environment
- Customizing minikube pipeline for your repository
- Validating Caddy routing configuration
When NOT to Use This Agent:
- When prerequisites haven't been validated yet
- When you're ready to configure Konflux pipelines directly
- For debugging test failures (use testing specialists)
- For complex Kubernetes troubleshooting
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 · 514 lines · 25 tokens per session scan A 4d64d6a35a65
hcc-frontend-konflux-local-testing-guide 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 25 tokens to every session and 3,827 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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-engineer
Integration Engineer responsible for connecting all components, creating Docker configuration, E2E verification, standard project files, and build validation.
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…