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 commands/openshift-eng/ai-helpers/payload-experimentgit 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/commands/openshift-eng/ai-helpers/payload-experiment)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/payload-experiment"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/payload-experiment.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.00022 | $0.01019 |
| Opus 5 | $0.00011 | $0.00509 |
| Sonnet 5 | $0.00004 | $0.00204 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
payload-experiment 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 6d 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:
- payload-experiment — 94% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:payload-experiment
Synopsis
/ci:payload-experiment <payload-tag>
Description
The ci:payload-experiment command opens draft revert PRs for medium-confidence payload candidates (confidence score 60-84) and triggers payload jobs to experimentally determine which PR is causing failures. It operates in two phases separated by a CI wait period.
Phase 1: Reads the payload results YAML, filters medium-confidence candidates, opens draft revert PRs, triggers payload jobs, and appends action entries (type: "experiment", status: "pending") to each candidate's actions array.
Phase 2: Detects candidates with a status: "pending" action entry in the results YAML, checks job results, promotes confirmed causes to real revert PRs (with TRT JIRA bugs), and closes innocent draft PRs.
All state is tracked in the payload results YAML via the payload-results-yaml skill — no separate tracking file is created.
This command is one of three composable stages in the payload triage pipeline:
/ci:payload-analysis— produces the payload results YAML/ci:payload-revert— stages reverts for HIGH confidence candidates/ci:payload-experiment— experimentally tests MEDIUM confidence candidates (this command)
Job Triggering Limits
- Non-aggregated jobs: Up to 5 total across all candidates
- Aggregated jobs: Up to 1 total
Implementation
-
Parse the payload tag from the argument. Extract
version,stream, andarchitecturefrom the tag (seepayload-analysisStep 1 for parsing rules). -
Read the payload results YAML using the
payload-results-yamlskill: Look forpayload-results-{tag}.yamlin the current working directory. If not found, print an error and exit:Error: Payload results YAML not found for {payload_tag}. Run `/ci:payload-analysis {payload_tag}` first to generate it. -
Detect Phase 2 resume: If the results YAML contains any action entry with
type: "experiment"andstatus: "pending", jump to Phase 2 (step 5). Phase 2 processes only pending experiments — candidates with other statuses are left unchanged.
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.
- 6d ago First seen · 82 lines · 22 tokens per session scan A 70c079dd8377
payload-experiment is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 1,019 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.