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 skills add openshift-eng/ai-helpers --skill payload-results-yamlgit 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/skills/openshift-eng/ai-helpers/payload-results-yaml)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/payload-results-yaml"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/payload-results-yaml/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/skills/openshift-eng/ai-helpers/payload-results-yaml"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/payload-results-yaml.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.03725 |
| Opus 5 | $0.00015 | $0.01862 |
| Sonnet 5 | $0.00006 | $0.00745 |
| Haiku 4.5 | $0.00003 | $0.00373 |
Grade A, and why
payload-results-yaml 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 yesterday.
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:
- Payload Results YAML — 89% identical, 101 lines differ
How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Payload Results YAML
This skill defines the schema for the payload-results-{tag}.yaml file and provides the operations for reading and writing it. All skills in the payload triage pipeline must use this skill when interacting with the results file.
When to Use This Skill
Use this skill whenever you need to:
- Create a new results file (during
payload-analysis) - Read candidates or their actions (during
payload-revert,payload-experiment) - Append an action to a candidate (during
stage-payload-reverts,payload-experimental-reverts) - Update an action's status (during
payload-experimental-revertsPhase 2)
File Location
The file is always written to and read from the current working directory:
payload-results-{tag}.yaml
Where {tag} is the full payload tag with colons and slashes replaced by hyphens (e.g., payload-results-4.22.0-0.nightly-2026-02-25-152806.yaml).
Schema
metadata:
payload_tag: "4.22.0-0.nightly-2026-02-25-152806"
version: "4.22"
stream: "nightly"
architecture: "amd64"
release_controller_url: "https://amd64.ocp.releases.ci.openshift.org/..."
analyzed_at: "2026-02-26T10:30:00Z"
force_accept_recommended: false
failing_jobs:
- job_name: "periodic-ci-...-e2e-aws-ovn"
prow_url: "https://prow.ci.openshift.org/..."
is_aggregated: false
underlying_job_name: ""
failure_type: "test"
root_cause_summary: "OVN gateway mode selection regression"
streak_length: 5
originating_payload_tag: "4.22.0-0.nightly-2026-02-20-150000"
failure_pattern: "F F F F F S S"
- job_name: "periodic-ci-...-e2e-gcp-ovn-techpreview"
prow_url: "https://prow.ci.openshift.org/..."
is_aggregated: false
underlying_job_name: ""
failure_type: "infra"
root_cause_summary: "Step pod unschedulable on build04: DiskPressure, 0/N nodes available"
streak_length: 1
originating_payload_tag: "4.22.0-0.nightly-2026-02-25-152806"
failure_pattern: "F"
ship_status:
component_slug: build-farm
sub_component_slug: build04
window_start: "2026-02-25T14:00:00Z"
window_end: "2026-02-25T15:30:00Z"
observed_health: healthy
existing_outage_id: null
queried_at: "2026-02-25T16:00:00Z"
action: pending
outage_id: null
dashboard_url: null
reason: ""
candidates:
- type: "pr"
pr_url: "https://github.com/openshift/cno/pull/2037"
pr_number: 2037
component: "cluster-network-operator"
title: "Fix OVN gateway mode selection"
confidence_score: 95
rationale: "temporal match + component match + error references code changed"
failing_jobs:
- "periodic-ci-...-e2e-aws-ovn"
actions:
- type: "revert"
status: "staged"
revert_pr_url: "https://github.com/openshift/cno/pull/2038"
revert_pr_state: "open"
result_summary: "Revert PR opened and payload jobs triggered"
jira_key: "TRT-1234"
jira_url: "https://redhat.atlassian.net/browse/TRT-1234"
payload_jobs:
- command: "/payload-job periodic-ci-...-e2e-aws-ovn"
test_url: "https://pr-payload-tests.ci.openshift.org/runs/ci/..."
test_prow_url: "https://prow.ci.openshift.org/view/gs/..."
- type: "rhcos_rpm"
rhcos_tag: "rhel-coreos-10"
rhcos_name: "Red Hat Enterprise Linux CoreOS 10.2"
package: "systemd"
old_version: "257-23.el10"
new_version: "257-23.el10_2.2"
confidence_score: 70
changelog_evidence: "systemd 257-23.el10_2.2: fix boot ordering race with local-fs-pre.target"
rationale: "systemd update correlates with variant-isolated boot timeout in RHCOS 10 jobs"
failing_jobs:
- "periodic-ci-...-e2e-metal-ipi-ovn-ipv4"
actions: []
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/test_validate.py 2.2 KB runs code
- scripts/testdata/invalid_candidate_type_not_string.yaml 385 B
- scripts/testdata/invalid_flat_schema.yaml 234 B
- scripts/testdata/invalid_metadata_string.yaml 58 B
- scripts/testdata/invalid_missing_job_fields.yaml 281 B
- scripts/testdata/invalid_rhcos_rpm_candidate.yaml 349 B
- scripts/testdata/invalid_ship_status_action_missing.yaml 529 B
- scripts/testdata/invalid_ship_status_action.yaml 320 B
- scripts/testdata/invalid_ship_status_null.yaml 302 B
- scripts/testdata/valid_no_candidates.yaml 280 B
- scripts/testdata/valid_with_rhcos_rpm_candidate.yaml 1.1 KB
- scripts/testdata/valid_with_ship_status.yaml 630 B
- scripts/testdata/valid.yaml 935 B
- scripts/validate.py 4.8 KB runs code
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.
- yesterday Changed ded86712fd34
- 9d ago First seen · 265 lines · 29 tokens per session scan A f04ab5b3ec1d
payload-results-yaml is a skill published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 3,725 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-09-03.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.