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.
npx skills add opendatahub-io/ai-helpers --skill konflux-applicationgit clone --depth 1 https://github.com/opendatahub-io/ai-helpersWrote 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/skills/opendatahub-io/ai-helpers/konflux-application)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/konflux-application"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/konflux-application/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/skills/opendatahub-io/ai-helpers/konflux-application"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/konflux-application.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00009 | $0.00545 |
| Opus 5 | $0.00005 | $0.00272 |
| Sonnet 5 | $0.00002 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
konflux-application 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 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.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
odh-ai-helpers:konflux-application
Synopsis
/konflux:application status <application>
Description
The konflux:application command to manage Konflux application.
This command helps you:
- List all components in the application
- Understand the status of the components in the application - last build, snapshots, releases
Implementation
Subcommand: status
The command performs the following steps:
-
Prerequisites Check:
- Verify
ocCLI is installed:which oc - Verify cluster access:
oc whoami - If not installed or not authenticated, provide clear instructions
- Verify
jqCLI is installed:which jq - Verify
gitCLI is installed:which git - Verify the current directory is a Git repository:
git remote -v
- Verify
-
Parse Arguments:
application: Application name (required)
-
List components that belong to the application:
- Get components
kubeclt get component -o yaml | jq '.items[] | select(.spec.application=="{application}") - The application name is provided in
.spec.application - The component name is provided in
.spec.componentName - The Git repository URL is provided in
.spec.source.git.url - The commit SHA is provided in
.status.lastBuiltCommit
- Get components
-
Show status for each Konflux component:
- Run the following command to get status of each Konflux component from the application
/konflux:component status {component}
Return Value
- status: Table of all components that belong to the provided application
Examples
- Get status all components of the otel-main application:
/konflux:application status otel-main
Arguments
status
- application (required): Name of the Konflux application
Troubleshooting
Related Commands
/konflux:component status <component>- Show component status/konflux:component build <components> [--wait <duration>] [--wait-release <duration>] [--nudge]- Trigger component build
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 · 85 lines · 9 tokens per session scan A d518c7a5e137
konflux-application is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed 4d ago), licensed Apache-2.0. It adds 9 tokens to every session and 545 once invoked, about $0.0000 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-30.
Other skills, from other repositories
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.
secrets-management
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
airflow-dag-patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.