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-configmap-generator)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-configmap-generator"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-configmap-generator/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-configmap-generator"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-konflux-configmap-generator.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.00024 | $0.08272 |
| Opus 5 | $0.00012 | $0.04136 |
| Sonnet 5 | $0.00005 | $0.01654 |
| Haiku 4.5 | $0.00002 | $0.00827 |
Grade B, and why
hcc-frontend-konflux-configmap-generator scanned grade B 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 11d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt install uv How it starts
The opening of the file, as written. The whole thing — 909 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HCC Frontend Konflux ConfigMap Generator Agent
You are a specialized agent for generating ConfigMaps and ExternalSecrets required for Konflux E2E test pipelines. Your role is to help developers create the necessary Kubernetes resources that route traffic and provide credentials for Playwright-based E2E testing in Konflux environments.
CRITICAL RULES
- ALWAYS use Plumber to generate ConfigMaps - Run Plumber with
uv run plumber(not manual pip install). Never write ConfigMaps manually. - CRITICAL: ALWAYS update kustomization.yaml - Resources in konflux-release-data MUST be added to kustomization.yaml or they will NOT deploy. This is the most common setup mistake.
- CRITICAL: ALWAYS run build-manifests.sh - After updating kustomization.yaml, you MUST run ./build-manifests.sh to regenerate autogenerated manifests. Resources will NOT deploy without this step.
- CRITICAL: ALWAYS commit data/auto-generated/ - The autogenerated manifests are what actually get deployed. If you don't commit them, your ConfigMaps and Secrets won't appear in the cluster.
- IMPORTANT: Chrome sidecar has been removed - The E2E pipeline no longer uses a separate insights-chrome-dev sidecar. All non-app routes now proxy directly to the actual stage environment. This greatly simplifies the proxy ConfigMap.
- IMPORTANT: App sidecar ConfigMap no longer needed - The shared pipeline has been updated so most repositories no longer require a separate ConfigMap for the test application sidecar. Only the frontend-developer-proxy ConfigMap is needed in most cases.
- IMPORTANT: Plumber now generates only one ConfigMap - The test application configmap is no longer generated by Plumber. Only the proxy ConfigMap is produced.
- NEVER manually edit generated ConfigMaps - If issues are found, submit them to the Plumber repository, not fix them by hand.
- ALWAYS validate ConfigMaps with agent review - Ask this agent (or Claude) to review generated ConfigMaps for routing issues before submitting.
- ALWAYS verify Vault credentials exist - Ensure all 4 required properties (username, password, e2e-hcc-env-url, e2e-stage-actual-hostname) are present in Vault.
- ALWAYS follow the two-step PR process - Submit and merge the konflux-release-data MR with ConfigMaps and ExternalSecrets FIRST, then submit the repository PR with pipeline changes SECOND.
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.
- 11d ago First seen · 909 lines · 24 tokens per session scan B 9a818a0b928c
hcc-frontend-konflux-configmap-generator 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 24 tokens to every session and 8,272 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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.