prepare

prepare is a command for Claude Code from openshift-eng/two-node-toolbox. It costs 14 tokens per session (2,164 once invoked), scanned A, original, Apache-2.0.

A command for preparing an OpenShift cluster configuration for dev-scripts, including a selected release image and environment checks. OpenShift is a platform for running containerised applications.

In plain words
What is it for?
Use it to prepare configurations for different cluster topologies, installation methods, cloud or external environments, IP versions, and processor architectures.
Why use it?
It creates and validates deployment configuration without deploying the cluster itself, reducing setup mistakes before a development environment is started.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to prepare configurations for different cluster topologies, installation methods, cloud or external environments, IP versions, and processor architectures.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/openshift-eng/two-node-toolbox/prepare
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.

Clone the repo
git clone --depth 1 https://github.com/openshift-eng/two-node-toolbox

Made for: Claude Code.

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 prepare

README.md
[![agentmods](https://agentmods.dev/badge/commands/openshift-eng/two-node-toolbox/prepare/github.svg)](https://agentmods.dev/commands/openshift-eng/two-node-toolbox/prepare)
Your own site
<a href="https://agentmods.dev/commands/openshift-eng/two-node-toolbox/prepare"><img src="https://agentmods.dev/badge/commands/openshift-eng/two-node-toolbox/prepare/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.

agentmods 80×15 button for prepare

Your own site · 80×15
<a href="https://agentmods.dev/commands/openshift-eng/two-node-toolbox/prepare"><img src="https://agentmods.dev/badge/commands/openshift-eng/two-node-toolbox/prepare.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,164 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00014 $0.02164
Opus 5.5 $0.00006 $0.00866
Sonnet 5.5 $0.00003 $0.00433
Haiku 4.5 $0.00001 $0.00216

Measured 22d ago against content hash 02d8b19c3547, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

prepare 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 22d 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.

.claude/commands/prepare.md · 205 lines

How it starts

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

You are preparing an OpenShift cluster configuration for deployment via dev-scripts. This skill resolves a release image, generates a config file, and validates the environment — but never deploys.

Arguments

/prepare <topology> <method> <medium> <version...> [key=value...]

Positional (required):

  • topology: tna / arbiter, tnf / fencing, or sno
  • method: ipi or agent
  • medium: aws or external
  • version: free text mapped to a resolver spec (see below)

Optional key=value overrides:

  • ip-stack=v4|v6|v4v6 (default: v4)
  • arch=x86_64|aarch64 (override auto-detection)
  • fencing-cred-id=hostname|macAddress (fencing topology only)
  • force=true (overwrite existing config)
  • ds-repo=URL (dev-scripts fork URL)
  • ds-branch=BRANCH (dev-scripts fork branch)

Version Mapping

The major version is not restricted to 4.x — any X.Y accepted by helpers/resolve-release-image.sh works (e.g. 5.1-nightly).

User says Resolver spec
4.21 nightly 4.21-nightly
latest 4.22 EC/RC 4.22-prerelease
4.22 EC 4.22-ec
4.20 or 4.20 GA 4.20
4.20.5 4.20.5
5.1 nightly 5.1-nightly
latest 5.2 EC/RC 5.2-prerelease
Contains / or @sha256: --pullspec (explicit)

Non-Interactive Contract

When all positional arguments are present, never prompt open-endedly. If prerequisites are missing, emit one consolidated failure block listing each issue with its fix, then stop:

Missing prerequisites:
- pull-secret.json: run /setup dev-scripts
- CI Token: run /setup, CI Token section
- inventory.ini: run /setup external (for external medium)

Interactive prompting is only for humans invoking with missing arguments.

Scope

Dev-scripts only (v1). No kcli, assisted, or baremetal-adopt. If the user asks for kcli or assisted, tell them it's out of scope and point to the relevant make targets.

CI Token Sourcing

  1. Check existing config/config_*.sh files for an active export CI_TOKEN="..." line (any topology)
  2. If found and not a placeholder (<PASTE), reuse it silently
  3. If not found: ask the human / fail the agent path with a pointer to /setup
  4. Never echo the token into chat output

Read the full file on GitHub · 205 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. 22d ago Changed · +5 lines 02d8b19c3547
  2. 29d ago First seen · 200 lines · 14 tokens per session scan A c7ba5f73abff

Subscribe to this mod's changes

prepare is a command published in the GitHub repository openshift-eng/two-node-toolbox (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,164 once invoked, about $0.0001 per session on Opus 5.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-09-19.