payload-revert

payload-revert is a command for Claude Code from wangke19/gemini-ai-helpers. It costs 13 tokens per session (781 once invoked), scanned A, a copy of payload-revert, Apache-2.0.

A command that reads payload-analysis results and prepares reversions for high-confidence candidates. In release engineering, a payload is a proposed software release, and a reversion undoes a change suspected of causing failures.

In plain words
What is it for?
Use it after payload analysis to create reverts for candidates scoring at least 85, open the related pull requests, and trigger their validation jobs within the stated limits.
Why use it?
It turns the highest-confidence findings into tracked Jira bugs, pull requests, and validation jobs instead of requiring each revert to be prepared manually.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

Good fit Use it after payload analysis to create reverts for candidates scoring at least 85, open the related pull requests, and trigger their validation jobs within the stated limits.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/wangke19/gemini-ai-helpers/payload-revert
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/wangke19/gemini-ai-helpers

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 payload-revert

README.md
[![agentmods](https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/payload-revert/github.svg)](https://agentmods.dev/commands/wangke19/gemini-ai-helpers/payload-revert)
Your own site
<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/payload-revert"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/payload-revert/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 payload-revert

Your own site · 80×15
<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/payload-revert"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/payload-revert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 781 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 91% copy Near-identical to another mod 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.00013 $0.00781
Opus 5 $0.00006 $0.00391
Sonnet 5 $0.00003 $0.00156
Haiku 4.5 $0.00001 $0.00078

Measured 9d ago against content hash 3de358160750, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

payload-revert 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 9d 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.

Origin

This is a copy

91% identical to payload-revert — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

extensions/ci/commands/payload-revert.md · 73 lines

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:payload-revert

Synopsis

/ci:payload-revert <payload-tag>

Description

The ci:payload-revert command reads the payload results YAML produced by /ci:analyze-payload and stages reverts for all high-confidence candidates (confidence score >= 85) that have not already been reverted.

For each qualifying candidate, it creates a TRT JIRA bug, opens a revert PR, and triggers payload validation jobs using the stage-payload-reverts skill.

This command is one of three composable stages in the payload triage pipeline:

  1. /ci:analyze-payload — produces the payload results YAML
  2. /ci:payload-revert — stages reverts for HIGH confidence candidates (this command)
  3. /ci:payload-experiment — opens draft revert PRs for MEDIUM confidence candidates

Job Triggering Limits

  • Non-aggregated jobs: Up to 5 total across all candidates
  • Aggregated jobs: Up to 1 total

When the number of failing jobs across all candidates exceeds these limits, prioritize jobs from higher-confidence candidates first.

Implementation

  1. Parse the payload tag from the argument. Extract version, stream, and architecture from the tag (see analyze-payload Step 1 for parsing rules).

  2. Read the payload results YAML using the payload-results-yaml skill: Look for payload-results-{tag}.yaml in the current working directory. If not found, print an error and exit:

    Error: Payload results YAML not found for {payload_tag}.
    Run `/ci:analyze-payload {payload_tag}` first to generate it.
    
  3. Filter candidates: Select candidates with confidence_score >= 85. Exclude any that already have an action with status of "open" or "merged" (pre-existing revert).

  4. Dispatch to stage-payload-reverts skill: Pass all qualifying candidates with their context (results YAML path, payload tag, version, stream, architecture, release controller URL, and failing jobs). The skill updates the results YAML and HTML report in place. The trigger-payload-job skill validates that aggregated jobs have underlying_job_name set and skips them with an error if not.

Read the full file on GitHub · 73 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. 9d ago First seen · 73 lines · 13 tokens per session scan A 3de358160750

Subscribe to this mod's changes

payload-revert is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 781 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to payload-revert, differing in 16 lines, and is treated as a copy.