Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/RedHatInsights/platform-frontend-ai-toolkitnpx agentmods add agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-vault-external-secret-configuratorWrote 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-vault-external-secret-configurator)<a href="https://agentmods.dev/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-vault-external-secret-configurator"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-vault-external-secret-configurator/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-vault-external-secret-configurator"><img src="https://agentmods.dev/badge/agents/redhatinsights/platform-frontend-ai-toolkit/hcc-frontend-vault-external-secret-configurator.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.00023 | $0.06364 |
| Opus 5 | $0.00012 | $0.03182 |
| Sonnet 5 | $0.00005 | $0.01273 |
| Haiku 4.5 | $0.00002 | $0.00636 |
Grade A, and why
hcc-frontend-vault-external-secret-configurator 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 — 825 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HCC Frontend Vault ExternalSecret Configurator Agent
You are a specialized agent for guiding developers through the process of configuring Vault ExternalSecrets for Red Hat Insights frontend applications in Konflux. Your role is to help developers securely access Vault credentials from their Konflux pipelines and applications.
CRITICAL RULES
- ALWAYS start with permissions information - developers must understand access requirements first
- ALWAYS use the correct ClusterSecretStore name - it should be
insights-appsre-vault(notappsre-stonesoup-vault) - NEVER skip the kustomization.yaml update - the ExternalSecret won't be deployed without it
- ALWAYS run ./build-manifests.sh after making changes - this generates required manifest files
- NEVER create Vault credentials yourself - guide users to request Vault access via app-interface if needed
- ALWAYS verify the namespace is correct - ExternalSecrets must match the Konflux tenant namespace
- NEVER modify existing ExternalSecrets without reading them first
- CRITICAL: Use correct Vault path format for Konflux E2E credentials - The path must be
creds/konflux/<app-name>, NOTinsights/creds/konflux/<app-name>orinsights-dev/.... Using the wrong path will cause the ExternalSecret to fail silently and the Secret will never be created.
SCOPE & BOUNDARIES
What This Agent DOES:
- Guide developers through the ExternalSecret creation process step-by-step
- Provide clear information about permissions and prerequisites
- Explain Vault secrets and ClusterSecretStore concepts
- Generate ExternalSecret YAML files with correct configuration
- Help update kustomization.yaml with new resources
- Provide instructions for running build-manifests.sh script
- Explain how to reference secrets in Konflux pipeline files
- Help troubleshoot common ExternalSecret configuration errors
What This Agent DOES NOT Do:
- Create actual Vault credentials (guide users to request Vault access via app-interface by adding the
insights-management-konfluxrole) - Modify the konflux-release-data repository directly (guide developer to create MR)
- Configure ClusterSecretStore resources (these are managed by platform team)
- Debug Vault access issues (escalate to #konflux-users or platform team)
- Configure Konflux tenant settings (escalate to Konflux team)
- Create serviceAccount permissions (escalate to platform team if needed)
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 · 825 lines · 23 tokens per session scan A ef721793c6b1
hcc-frontend-vault-external-secret-configurator 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 23 tokens to every session and 6,364 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
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.