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/fetch-payloadsgit 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/fetch-payloads)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/fetch-payloads"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/fetch-payloads.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 | $0.00011 | $0.00729 |
| Opus 5 | $0.00005 | $0.00365 |
| Sonnet 5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade B, and why
fetch-payloads scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
FETCH_PAYLOADS=$(find ~/.claude/plugins -type f -path "*/ci/skills/fetch-payloads/fetch_payloads.py" 2>/dev/null | sort | head -1) Copies of this mod
1 near-identical copy found in the catalogue:
- fetch-payloads — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:fetch-payloads
Synopsis
/ci:fetch-payloads [architecture] [version] [stream]
Description
The ci:fetch-payloads command fetches recent release payloads from the OpenShift release controller. It shows each payload's tag name, phase (Accepted/Rejected/Ready), timestamp, and blocking job results. For rejected payloads, it reports which blocking jobs failed with Prow links.
Implementation
-
Determine parameters: Default to
amd64architecture andnightlystream if the user hasn't specified them. If no version is provided, the script fetches the latest from the Sippy API. -
Fetch payloads: Use the
fetch-payloadsskill:FETCH_PAYLOADS="${CLAUDE_PLUGIN_ROOT}/skills/fetch-payloads/fetch_payloads.py" if [ ! -f "$FETCH_PAYLOADS" ]; then FETCH_PAYLOADS=$(find ~/.claude/plugins -type f -path "*/ci/skills/fetch-payloads/fetch_payloads.py" 2>/dev/null | sort | head -1) fi if [ -z "$FETCH_PAYLOADS" ] || [ ! -f "$FETCH_PAYLOADS" ]; then echo "ERROR: fetch_payloads.py not found" >&2; exit 2; fi python3 "$FETCH_PAYLOADS" [architecture] [version] [stream]Optional flags:
--phase Accepted|Rejected|Readyto filter by phase--limit Nto control how many results to show (default 5)
-
Present the results: Show the user the payload list. For rejected payloads, highlight the failed blocking jobs and their Prow links.
Return Value
- Format: One block per payload with tag, phase, timestamp, URL, and job details
- Rejected payloads: Each failed blocking job is listed with retry count and Prow link
- Ready payloads: Summary of succeeded/pending/failed blocking job counts
- Accepted payloads: Confirmation that all blocking jobs succeeded
Examples
-
Latest nightly payloads (defaults to amd64, latest version, last 5):
/ci:fetch-payloads -
Specific version and architecture:
/ci:fetch-payloads arm64 4.18 nightly -
Only accepted payloads:
/ci:fetch-payloads amd64 4.23 nightly --phase Accepted
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.
- 5d ago First seen · 73 lines · 11 tokens per session scan B 8e1391d2dd6a
fetch-payloads is a command published in the GitHub repository openshift-eng/ai-helpers (114 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 729 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.