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 wangke19/gemini-ai-helpers --skill revert-prgit 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/skills/wangke19/gemini-ai-helpers/revert-pr)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/revert-pr"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/revert-pr/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/wangke19/gemini-ai-helpers/revert-pr"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/revert-pr.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.00018 | $0.04538 |
| Opus 5 | $0.00009 | $0.02269 |
| Sonnet 5 | $0.00004 | $0.00908 |
| Haiku 4.5 | $0.00002 | $0.00454 |
Grade A, and why
Revert PR 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 10d 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
94% identical to revert-pr — 10 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 — 473 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revert PR
This skill provides the detailed git revert workflow and the exact PR body template used by Revertomatic for reverting merged pull requests that break CI or nightly payloads.
When to Use This Skill
Use this skill when:
- A merged PR needs to be reverted to restore CI signal
- Following the OpenShift quick-revert policy
- You need the exact Revertomatic template format for the revert PR body
- You need to generate CI override commands for a revert PR
Optional Parameters
--draft: When set, create the revert PR as a draft (gh pr create --draft). Used by the experimental revert workflow to open experimental revert PRs that may be closed if the suspect is cleared.--context: When the caller passes context directly (e.g., from an autonomous pipeline that already has all context in memory), skip the JIRA lookup in Step 5. The provided context string is used as-is for the{CONTEXT}template variable.
Prerequisites
-
GitHub CLI (
gh): Installed and authenticated- Check:
gh auth status
- Check:
-
Git: Installed and configured
- Check:
which git
- Check:
-
Repository Access: User must have push access to their fork of the target repository
Implementation Steps
Step 1: Extract PR Information
Use the gh CLI to fetch all necessary details about the PR being reverted:
# Fetch PR details as JSON
pr_data=$(gh pr view "$PR_URL" --json number,title,author,mergeCommit,baseRefName,state)
# Extract fields
pr_number=$(echo "$pr_data" | jq -r '.number')
pr_title=$(echo "$pr_data" | jq -r '.title')
pr_author=$(echo "$pr_data" | jq -r '.author.login')
merge_sha=$(echo "$pr_data" | jq -r '.mergeCommit.oid')
base_branch=$(echo "$pr_data" | jq -r '.baseRefName')
pr_state=$(echo "$pr_data" | jq -r '.state')
Validation:
pr_statemust beMERGED. If the PR is not merged, abort with an error.merge_shamust not be empty or null.
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.
- 10d ago First seen · 473 lines · 18 tokens per session scan A 223a86b42d47
Revert PR is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 4,538 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to revert-pr, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
ccmanager-config
Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global /.config/ccmanager/config.json. Use when someone wants ccmanager to launch a different agent CLI (codex, gemini, cursor-agent, copilot…), add command presets, run a command on session state changes or worktree…
github-release-notes-writer
Draft or update user-focused GitHub Release Notes from verified tags, commits, pull requests, existing releases, and supplied changelog baselines. Use when preparing prerelease or stable release notes, turning GitHub's generated What's Changed list into a curated narrative, documenting upgrades or breaking changes, or…
otel-changelog-pr-verifier
Verify whether CHANGELOG entries in an OpenTelemetry Go repository point to the correct pull requests and whether each (#NNNN) matches the described change. Use when checking a release PR, validating a CHANGELOG section, or screening only mismatched changelog-to-PR references.
lov-git-commit-with-context
A Git commit helper that compares the current conversation's intended work with the repository's actual changes before creating a commit. Git is a system for tracking file changes, and a commit records a selected set of those changes.
intuitive-port-worktree
Port changes from one git worktree or checkout into the default repository folder's current branch, then by default sync the result to the remote default branch when everything is clean. Use when the user asks to move, copy, transfer, transplant, cherry-pick, apply a patch, or port worktree changes into the…
chinese-commit-conventions
A Chinese-language convention for writing Git commit messages, based on Conventional Commits, a standard format that tools can use to classify changes and build changelogs.