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/analyze-pr-reverts)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/analyze-pr-reverts"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/analyze-pr-reverts/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/analyze-pr-reverts"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/analyze-pr-reverts.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.00012 | $0.02124 |
| Opus 5 | $0.00006 | $0.01062 |
| Sonnet 5 | $0.00002 | $0.00425 |
| Haiku 4.5 | $0.00001 | $0.00212 |
Grade A, and why
analyze-pr-reverts scanned grade A 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s 'https://sippy.dptools.openshift.org/api/pull_requests?release=Presubmits&filter=%7B%22items%22%3A%5B%7B%22columnField%22%3A%22title%22%2C%22operatorValue%22%3A%22contains%22%2C%22value%22%3A%22revert%22%7D%5D%2C This is a copy
100% identical to analyze-pr-reverts — 0 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:analyze-pr-reverts
Synopsis
/ci:analyze-pr-reverts [limit]
Description
The ci:analyze-pr-reverts command fetches recently reverted pull requests from the Sippy API and analyzes them to identify common failure patterns, the most affected repositories, and recommends concrete preventive measures such as new presubmit jobs, org-wide CodeRabbit review rules, or process changes.
This command is intended to be run periodically (e.g., monthly) to track revert trends over time.
Implementation
-
Fetch Revert PRs from Sippy API: Query the Sippy API for PRs with "revert" in the title.
curl -s 'https://sippy.dptools.openshift.org/api/pull_requests?release=Presubmits&filter=%7B%22items%22%3A%5B%7B%22columnField%22%3A%22title%22%2C%22operatorValue%22%3A%22contains%22%2C%22value%22%3A%22revert%22%7D%5D%2C%22linkOperator%22%3A%22and%22%7D&sortField=merged_at&sort=desc&limit=<LIMIT>'- The default limit is 50 but can be overridden by the user's argument
- The API returns JSON with fields including:
merged_at,link,author,title - Parse the JSON response and extract all PR entries
-
Deduplicate: Remove duplicate entries (same PR URL appearing multiple times).
-
Scrape PR Details: For each unique PR URL, fetch details using
gh:gh pr view <url> --json title,body,files,labelsExtract from each PR:
- Repository: Parse org/repo from the URL
- Description: The PR body explaining why the revert was needed
- Files changed: What areas of code were affected
- Root cause category: Classify based on the description (see categories below)
If a PR cannot be fetched (permissions, deleted, etc.), note it and continue.
-
Categorize Each Revert: Classify each revert into one or more of these root cause categories based on the PR description and the original PR that was reverted:
- Test/platform coverage gap: New or migrated tests that fail on untested platforms (microshift, single-node, IPv6, FIPS, real-time, upgrade jobs). Look for mentions of specific failing job profiles.
- IPv6/network incompatibility: Changes that work on IPv4 but break IPv6/dual-stack clusters. Look for hardcoded IPv4 addresses, network bind issues.
- Operator/controller regression: Core operator logic changes causing CrashLoopBackOff, degraded states, install failures, or functional breakage.
- Build/CI tooling: Renovate configs, dependency automation, build pipeline changes that break CI.
- API/validation side effects: API changes, CRD validation changes, or policy enforcement that has unexpected downstream impact.
- Feature flag/config change: Premature feature gate removal, default value changes, config toggles.
- Cross-component dependency: Change that depends on another component's change that hasn't landed or built yet.
- Flaky/unstable new test: New test that passes sometimes but flakes at a high enough rate to block payloads.
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.
- 11d ago First seen · 171 lines · 12 tokens per session scan A 2f50243c75b7
analyze-pr-reverts is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 2,124 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to analyze-pr-reverts, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
5_gofer_implement
Execute all tasks from tasks.md phase by phase with feedback loops and engineering review.
eai-update
Use this command to install or update EAI Gofer for the current AI coding app. This command works without an EAI project, a Gofer scaffold, or EAI sign-in.
modernize-extract-rules
Mine business logic from legacy code into testable, human-readable rule specifications.
mem-search
Full-text search in the memory vault (archives, contexts, histories, index).
help
Get help with the hookify plugin.
checklist
Generate a custom checklist for the current feature based on user requirements.