list-step

list-step is a command for coding agents from openshift-eng/ai-helpers. It costs 10 tokens per session (1,300 once invoked), scanned A, original, Apache-2.0.

A command that lists every part of an OpenShift continuous-integration workflow or chain, including its referenced files and repository paths.

In plain words
What is it for?
It helps inspect a named CI workflow or chain and see its full hierarchy, including the main file, linked chains, references, and commands.
Why use it?
It removes the need to trace nested workflow, chain, and reference files manually.

Command

Part of the ci plugin — 10 skills, 21 commands, 2 agents shipped together

Install

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.

agentmods
npx agentmods add commands/openshift-eng/ai-helpers/list-step
Clone the repo
git clone --depth 1 https://github.com/openshift-eng/ai-helpers

Or install ci, the plugin that ships this one along with the rest of its 10 skills, 21 commands, 2 agents.

Wrote 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.

agentmods badge for list-step

README.md
[![agentmods](https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/list-step.svg)](https://agentmods.dev/commands/openshift-eng/ai-helpers/list-step)
Your own site
<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/list-step"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/list-step.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,300 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.01300
Opus 5 $0.00005 $0.00650
Sonnet 5 $0.00002 $0.00260
Haiku 4.5 $0.00001 $0.00130

Measured 4d ago against content hash 2c94e2643d49, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

list-step 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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • list-step — 97% identical, 2 lines differ
plugins/ci/commands/list-step.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Name

ci:list-step

Synopsis

/ci:list-step

Description

The ci:list-step command analyzes an OpenShift CI workflow or chain and provides a complete hierarchical breakdown of all the workflow, chain, and ref files with their repo paths that make up the workflow or chain.

The command accepts:

  • Workflow/Chain name (required)

It uses the step-registry-analyzer agent to examine the workflow/chain structure and identify all related components including workflows, chains, refs, and their associated command files.

Implementation

The command performs the following steps:

  1. Parse Arguments:
    • $1: Workflow or chain name (required, e.g., "hypershift-aws-reqserving-e2e")
  2. Execute Analysis: Use the Task tool with step-registry-analyzer agent: Task tool with:
  • subagent_type: "step-registry-analyzer"
  • description: "analyze and list all workflow/chain/ref with repository path for and keep the hierarchical structure"
  • prompt: Detailed request to analyze the workflow or chain and provide complete hierarchical breakdown
  1. Display Results: Present the hierarchical structure showing:
    • Main workflow or chain file path
    • All chain files referenced in the workflow or chain with their repository paths
    • All ref files referenced in the chains with their repository paths
    • Any command files (.sh) associated with the refs
    • The complete hierarchical structure showing relationships between all files
  2. Format Output: Use a clear hierarchical tree format with:
    • Full repository paths for all files
    • Indentation showing the workflow/chain/ref relationships
    • File types (workflow/chain/ref/command) clearly identified
    • Summary of total files and execution phases

Return Value

  • Success: Complete hierarchical structure of the OpenShift CI workflow or chain
  • Error: Workflow or Chain not found, analysis failure, or invalid workflow or chain name

Important for Claude:

  1. REQUIRED: Always use the step-registry-analyzer agent for this analysis
  2. Use the Task tool with the specialized agent to ensure comprehensive analysis
  3. Maintain the proper directory structure and show the relationships between files
  4. Include all phases (PRE/TEST/POST) in the hierarchy
  5. Show both the structural hierarchy and file paths clearly
  6. Show all workflow/chain/ref/command files with repository path
  7. Provide a summary of total files and execution flow

Read the full file on GitHub · 124 lines

Changes

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.

  1. 4d ago First seen · 124 lines · 10 tokens per session scan A 2c94e2643d49

Subscribe to this mod's changes

list-step is a command published in the GitHub repository openshift-eng/ai-helpers (114 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 1,300 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-30.