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.
git clone --depth 1 https://github.com/wangke19/gemini-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/wangke19/gemini-ai-helpers/payload-revert)<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.
<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>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.00013 | $0.00781 |
| Opus 5 | $0.00006 | $0.00391 |
| Sonnet 5 | $0.00003 | $0.00156 |
| Haiku 4.5 | $0.00001 | $0.00078 |
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.
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.
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:
/ci:analyze-payload— produces the payload results YAML/ci:payload-revert— stages reverts for HIGH confidence candidates (this command)/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
-
Parse the payload tag from the argument. Extract
version,stream, andarchitecturefrom the tag (seeanalyze-payloadStep 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:analyze-payload {payload_tag}` first to generate it. -
Filter candidates: Select candidates with
confidence_score >= 85. Exclude any that already have an action withstatusof"open"or"merged"(pre-existing revert). -
Dispatch to
stage-payload-revertsskill: 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. Thetrigger-payload-jobskill validates that aggregated jobs haveunderlying_job_nameset and skips them with an error if not.
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.
- 9d ago First seen · 73 lines · 13 tokens per session scan A 3de358160750
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.
Other commands, from other repositories
worktree
Set up parallel agent sessions on independent tasks via git worktrees. Use when asked to '/worktree', 'git worktree', 'parallel branches', 'isolated branch workspace', 'work on two things at once'.
wtfp:update
Check for a newer compatible package or plugin release and install it only after approval.
mem-archeo-git
Phase 3 of the triphasic archeo: reconstruct the Git history of an existing repo as dated archives, enriched by the topology and stack from Phases 0/1/2.
careful
Warn before destructive commands (rm -rf, DROP TABLE, git push --force, docker prune). Pairs with /freeze and /guard. Inspired by gstack.
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.