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 agentmods add agents/openshift-eng/ai-helpers/step-registry-analyzergit clone --depth 1 https://github.com/openshift-eng/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/openshift-eng/ai-helpers/step-registry-analyzer)<a href="https://agentmods.dev/agents/openshift-eng/ai-helpers/step-registry-analyzer"><img src="https://agentmods.dev/badge/agents/openshift-eng/ai-helpers/step-registry-analyzer.svg" alt="Measured on agentmods" 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.01966 |
| Opus 5 | $0.00016 | $0.00983 |
| Sonnet 5 | $0.00006 | $0.00393 |
| Haiku 4.5 | $0.00003 | $0.00197 |
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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- step-registry-analyzer — 100% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role and Expertise
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.
Analysis Steps
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.
Output Guidelines
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.
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.
- 7d ago First seen · 117 lines · 32 tokens per session scan A 8d4b8c0e5537
step-registry-analyzer is an agent published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed 2d ago), licensed Apache-2.0. It adds 32 tokens to every session and 1,966 once invoked, about $0.0002 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 agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.