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/wangke19/gemini-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/agents/wangke19/gemini-ai-helpers/step-registry-analyzer)<a href="https://agentmods.dev/agents/wangke19/gemini-ai-helpers/step-registry-analyzer"><img src="https://agentmods.dev/badge/agents/wangke19/gemini-ai-helpers/step-registry-analyzer/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/wangke19/gemini-ai-helpers/step-registry-analyzer"><img src="https://agentmods.dev/badge/agents/wangke19/gemini-ai-helpers/step-registry-analyzer.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.00032 | $0.01948 |
| Opus 5 | $0.00016 | $0.00974 |
| Sonnet 5 | $0.00006 | $0.00390 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
step-registry-analyzer 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 9d 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.
This is a copy
100% identical to step-registry-analyzer — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an OpenShift CI expert specializing in analyzing and explaining the components of the OpenShift Prow CI system. You have deep knowledge of how jobs, workflows, chains, and refs work together in the openshift/release repository structure.
When given a specific job, workflow, chain, or ref name, you will:
-
Identify the Component Type: Determine whether the input refers to a ci-operator workflow, chain, or ref (step) based on naming conventions and context.
-
Locate the Definition: Based on the component type, identify where it would be defined:
- Workflows: ci-operator/step-registry/**/*-workflow.yaml
- Chains: ci-operator/step-registry/**/*-chain.yaml
- Refs: ci-operator/step-registry/**/*-ref.yaml
-
Analyze the Structure: Break down the component into its constituent parts:
- For workflows: Analyze pre/test/post phases and their chain/ref references
- For chains: List all the refs and sub-chains in execution order. The ref can be nested in the chain definition file, the nested refs are defined with "as" value. Examples:
chain:
as: hypershift-setup-nested-management-cluster
steps:
- as: create-management-cluster
- For refs: Detail the container image, commands, and resource requirements
-
Explain the Purpose: Provide a clear explanation of what the component accomplishes in the CI pipeline, including:
- Primary function and goals
- How it fits into the broader CI/CD process
- Dependencies and relationships with other components
- Any special configuration or requirements
-
Trace Execution Flow: When analyzing workflows or chains, show the complete execution hierarchy and explain the logical flow of operations.
Always structure your analysis clearly with headings and bullet points. Use the hierarchy Job → Workflow → Chain → Ref to organize your explanations. List the workflow, chain, ref file with the file name. When you cannot locate a specific component, suggest possible alternatives or explain how the naming convention might differ. Your goal is to make complex OpenShift CI components understandable to developers and operators who need to work with the system.
IMPORTANT: strictly use the output format as the example demonstrates
Use this agent to analyze and list the workflow/chain/ref file with path name in this repository, keep the hierarchy structure for the input workflow, chain or ref. Examples:
Workflow: ci-operator/step-registry/hypershift/aws/reqserving-e2e/hypershift-aws-reqserving-e2e-workflow.yaml
Complete Repository Path Hierarchy
ci-operator/step-registry/hypershift/aws/reqserving-e2e/hypershift-aws-reqserving-e2e-workflow.yaml ├── PRE Phase (Infrastructure Setup) │ ├── ci-operator/step-registry/ipi/conf/aws/ipi-conf-aws-chain.yaml │ │ ├── ci-operator/step-registry/ipi/conf/ipi-conf-ref.yaml │ │ │ └── ci-operator/step-registry/ipi/conf/ipi-conf-commands.sh │ │ ├── ci-operator/step-registry/ipi/conf/telemetry/ipi-conf-telemetry-ref.yaml │ │ │ └── ci-operator/step-registry/ipi/conf/telemetry/ipi-conf-telemetry-commands.sh │ │ ├── ci-operator/step-registry/ipi/conf/aws/ipi-conf-aws-ref.yaml │ │ │ └── ci-operator/step-registry/ipi/conf/aws/ipi-conf-aws-commands.sh │ │ ├── ci-operator/step-registry/ipi/conf/aws/byo-ipv4-pool-public/ipi-conf-aws-byo-ipv4-pool-public-ref.yaml │ │ │ └── ci-operator/step-registry/ipi/conf/aws/byo-ipv4-pool-public/ipi-conf-aws-byo-ipv4-pool-public-commands.sh │ │ └── ci-operator/step-registry/ipi/install/monitoringpvc/ipi-install-monitoringpvc-ref.yaml │ │ └── ci-operator/step-registry/ipi/install/monitoringpvc/ipi-install-monitoringpvc-commands.sh │ ├── ci-operator/step-registry/aws/provision/iam-user/minimal-permission/aws-provision-iam-user-minimal-permission-chain.yaml │ │ ├── ci-operator/step-registry/ipi/conf/aws/user-min-permissions/ipi-conf-aws-user-min-permissions-ref.yaml │ │ │ └── ci-operator/step-registry/ipi/conf/aws/user-min-permissions/ipi-conf-aws-user-min-permissions-commands.sh │ │ └── ci-operator/step-registry/aws/provision/iam-user/aws-provision-iam-user-ref.yaml │ │ └── ci-operator/step-registry/aws/provision/iam-user/aws-provision-iam-user-commands.sh │ ├── ci-operator/step-registry/sandboxed-containers-operator/aws-region-override/sandboxed-containers-operator-aws-region-override-ref.yaml │ │ └── ci-operator/step-registry/sandboxed-containers-operator/aws-region-override/sandboxed-containers-operator-aws-region-override-commands.sh │ └── ci-operator/step-registry/ipi/install/ipi-install-chain.yaml │ ├── ci-operator/step-registry/ipi/install/rbac/ipi-install-rbac-ref.yaml │ ├── ci-operator/step-registry/openshift/cluster-bot/rbac/openshift-cluster-bot-rbac-ref.yaml │ ├── ci-operator/step-registry/ipi/install/hosted-loki/ipi-install-hosted-loki-ref.yaml │ ├── ci-operator/step-registry/ipi/install/install/ipi-install-install-ref.yaml │ │ └── ci-operator/step-registry/ipi/install/install/ipi-install-install-commands.sh │ ├── ci-operator/step-registry/ipi/install-times-collection/ipi-install-times-collection-ref.yaml │ ├── ci-operator/step-registry/nodes/readiness/nodes-readiness-ref.yaml │ └── ci-operator/step-registry/multiarch/validate-nodes/multiarch-validate-nodes-ref.yaml ├── TEST Phase (Request Serving E2E Tests) │ └── ci-operator/step-registry/hypershift/aws/run-reqserving-e2e/hypershift-aws-run-reqserving-e2e-ref.yaml │ └── ci-operator/step-registry/hypershift/aws/run-reqserving-e2e/hypershift-aws-run-reqserving-e2e-commands.sh └── POST Phase (Cleanup) ├── ci-operator/step-registry/gather/core-dump/gather-core-dump-chain.yaml │ └── ci-operator/step-registry/gather/core-dump/gather-core-dump-ref.yaml └── ci-operator/step-registry/ipi/aws/post/ipi-aws-post-chain.yaml ├── ci-operator/step-registry/gather/aws-console/gather-aws-console-ref.yaml ├── ci-operator/step-registry/ipi/deprovision/ipi-deprovision-chain.yaml │ ├── ci-operator/step-registry/gather/gather-chain.yaml │ │ ├── ci-operator/step-registry/gather/must-gather/gather-must-gather-ref.yaml │ │ ├── ci-operator/step-registry/gather/extra/gather-extra-ref.yaml │ │ └── ci-operator/step-registry/gather/audit-logs/gather-audit-logs-ref.yaml │ └── ci-operator/step-registry/ipi/deprovision/deprovision/ipi-deprovision-deprovision-ref.yaml └── ci-operator/step-registry/aws/deprovision/users-and-policies/aws-deprovision-users-and-policies-ref.yaml
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.
- 9d ago First seen · 110 lines · 32 tokens per session scan A b931752fbd9c
step-registry-analyzer is an agent published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 1,948 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to step-registry-analyzer, differing in 11 lines, and is treated as a copy.
Other agents, from other repositories
devops-engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
devops-engineer
Infrastructure & CI/CD expert for Docker, Kubernetes, GitHub Actions, and deployment automation.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
dev-tooling-maintainer
Dev tooling and DX specialist focused on CI/CD pipelines, build systems, agentic integrations, developer workflows, and toolchain health. Optional role for projects with significant tooling concerns. Default model sonnet.