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/revert-prgit 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/revert-pr)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/revert-pr"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/revert-pr.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.00013 | $0.01536 |
| Opus 5 | $0.00006 | $0.00768 |
| Sonnet 5 | $0.00003 | $0.00307 |
| Haiku 4.5 | $0.00001 | $0.00154 |
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 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- revert-pr — 94% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:revert-pr
Synopsis
/ci:revert-pr <pr-url> <jira-ticket>
Description
The ci:revert-pr command reverts a merged pull request that is breaking CI or nightly payloads. It follows the OpenShift quick-revert policy to restore CI signal.
This command:
- Extracts the original PR details (title, author, merge commit SHA, base branch)
- Ensures the user has a fork of the repository
- Creates a revert branch and performs
git revert -m1of the merge commit - Pushes the revert branch to the user's fork
- Creates a revert PR using the Revertomatic template format
- Generates a list of CI override commands (
/override) for jobs that may need to be bypassed on the revert PR
This command is useful when:
- A merged PR is causing CI job failures
- Nightly payloads are blocked by a breaking change
- Quick reversion is needed to restore CI signal while the original author fixes the issue
Implementation
-
Parse Arguments: Extract the PR URL, JIRA ticket, and flags
- PR URL format:
https://github.com/{owner}/{repo}/pull/{number} - JIRA ticket: e.g.,
TRT-1234orOCPBUGS-56789 - If the user provides additional context about why the revert is needed, capture it for the PR body
- If the user provides verification details (jobs to run before unrevert), capture those too
- PR URL format:
-
Gather Context: Use the JIRA ticket to automatically determine what broke and what needs verification
- Look up the JIRA ticket using the
fetch-jira-issueskill (plugins/ci/skills/fetch-jira-issue/fetch_jira_issue.py) with--format json - Extract context from the JIRA issue: Use the issue summary, description, and comments to determine:
- What broke: Which CI jobs or payloads are failing (e.g., "e2e-aws jobs failing on 4.18 nightly payload")
- Verification jobs: Which jobs should pass before the original change can be re-landed (e.g., "e2e-aws, e2e-gcp")
- Compose the context for the revert PR body from the JIRA issue details. Include links to failing jobs or payloads if mentioned in the ticket.
- Fall back to asking the user only if:
- The JIRA lookup fails (token not set, network error, ticket not found)
- The JIRA issue doesn't contain enough information to determine what broke or which jobs to verify
- If the user provided additional context as inline arguments, combine it with the JIRA-derived context
- Look up the JIRA ticket using the
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 · 129 lines · 13 tokens per session scan A 96ec47c4cc1d
revert-pr is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 1,536 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.