hypershift: Skill for Claude Code

.claude/skills/test-tag-pipeline/SKILL.md

test-tag-pipeline is a skill for Claude Code from openshift/hypershift. It costs 18 tokens per session (1,080 once invoked), scanned A, original, Apache-2.0.

A procedure for creating a manual PipelineRun, which is one execution of a build pipeline, for an existing Git tag. It tests pipeline changes against that tag before the changes are merged.

In plain words
What is it for?
Use it to test a tagged release with a pipeline from a branch, including branches from a fork, after checking access and resolving the tag's commit.
Why use it?
It lets you verify a changed tag pipeline without waiting for the normal process or rebuilding the wrong source revision. It also reports the created run so it can be monitored.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is openshift/hypershift's own configuration. It tells Claude Code how to work on hypershift itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hypershift configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash hack/tools/scripts/create-manual-tag-pipelinerun.sh {{args.0}} {{args.1:-main}}.

Part of the hypershift plugin — 22 skills, 5 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to openshift/hypershift. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/openshift/hypershift/main/.claude/skills/test-tag-pipeline/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/openshift/hypershift

Made for: Claude Code.

Or install hypershift, the plugin that ships this one along with the rest of its 22 skills, 5 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 test-tag-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/openshift/hypershift/test-tag-pipeline.svg)](https://agentmods.dev/skills/openshift/hypershift/test-tag-pipeline)
Your own site
<a href="https://agentmods.dev/skills/openshift/hypershift/test-tag-pipeline"><img src="https://agentmods.dev/badge/skills/openshift/hypershift/test-tag-pipeline.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,080 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00018 $0.01080
Opus 5 $0.00009 $0.00540
Sonnet 5 $0.00004 $0.00216
Haiku 4.5 $0.00002 $0.00108

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

Security

Grade A, and why

test-tag-pipeline 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 8d 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/skills/test-tag-pipeline/SKILL.md · 101 lines

What it actually says

Create a manual PipelineRun to test tag pipeline changes before merging.

Usage: /test-tag-pipeline <tag-name> [branch-spec]

Arguments:

  • tag-name (required): The existing tag to rebuild (e.g., v0.1.69)
  • branch-spec (optional): The branch containing the updated pipeline (defaults to main)
    • Format: [fork:]branch-name
    • If no fork specified, defaults to openshift

What this does:

  1. Verifies you are logged into the Konflux instance
  2. Gets the commit SHA that the tag points to
  3. Fetches the tag pipeline definition from the specified branch/fork
  4. Replaces template variables with actual values for the tag
  5. Creates a manual PipelineRun that uses the updated pipeline to build the tag's commit
  6. Outputs the PipelineRun name for monitoring

Examples:

# Test main branch pipeline with v0.1.69 tag
/test-tag-pipeline v0.1.69

# Test PR branch pipeline with v0.1.69 tag
/test-tag-pipeline v0.1.69 build-gomaxprocs-image

# Test fork branch pipeline with v0.1.69 tag
/test-tag-pipeline v0.1.69 celebdor:OCPBUGS-63194-part2

Implementation:

IMPORTANT: Execute the commands exactly as shown with only the arguments provided by the user. If no branch argument is specified, the template {{args.1:-main}} will correctly default to main. Do NOT substitute the current git branch or any other inferred values.

Step 1: Verify authentication to Konflux

oc whoami

If the authentication check fails, inform the user they need to log in first:

oc login --web https://api.stone-prd-rh01.pg1f.p1.openshiftapps.com:6443

Step 2: Create the PipelineRun

bash hack/tools/scripts/create-manual-tag-pipelinerun.sh {{args.0}} {{args.1:-main}}

After the PipelineRun is created, extract the name from the output and construct the web UI URL:

Example: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/crt-redhat-acm-tenant/applications/hypershift-operator/pipelineruns/hypershift-operator-main-manual-v0.1.69-xxxxx

Display the full URL to the user so they can monitor progress in the web UI.

You can also monitor it from the CLI with:

# Watch the PipelineRun status
oc get pipelinerun <name> -w

Step 3: After the PipelineRun completes successfully, create a Snapshot to trigger Enterprise Contract validation:

bash hack/tools/scripts/create-snapshot-from-pipelinerun.sh <pipelinerun-name>

After the Snapshot is created, extract the snapshot name from the output and get the EC PipelineRuns:

oc get pipelinerun -l appstudio.openshift.io/snapshot=<snapshot-name> -o name

For each EC PipelineRun, construct and display the web UI URL:

Example: https://konflux-ui.apps.stone-prd-rh01.pg1f.p1.openshiftapps.com/ns/crt-redhat-acm-tenant/applications/hypershift-operator/pipelineruns/hypershift-operator-enterprise-contract-xxxxx

Display the full URLs to the user so they can monitor EC validation in the web UI.

You can also monitor from the CLI with:

# Watch the snapshot status
oc get snapshot <snapshot-name> -w

# Check EC test results
oc get pipelinerun -l appstudio.openshift.io/snapshot=<snapshot-name>

Notes:

  • This is useful for testing pipeline fixes before merging PRs
  • The PipelineRun uses the updated pipeline definition but builds the original tag's commit
  • The two-step process allows the PipelineRun to complete (20+ minutes) before creating the Snapshot
  • Requires yq and oc CLI tools to be installed
  • See hack/tools/scripts/create-manual-tag-pipelinerun.sh and hack/tools/scripts/create-snapshot-from-pipelinerun.sh for implementation details
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. 8d ago First seen · 101 lines · 18 tokens per session scan A 10f4fcb6130a

Subscribe to this mod's changes

test-tag-pipeline is a skill published in the GitHub repository openshift/hypershift (540 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 1,080 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.

Related

Other skills, from other repositories

import-prom-rule

Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…

ccfos/nightingale · 125 tokens

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

configure-env-variables

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…

microsoft/power-platform-skills · 119 tokens

atmos-profiles

Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.

cloudposse/atmos · 35 tokens

webhook-management

Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.

hoangsonww/Claude-Code-Agent-Monitor · 56 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens