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/dmzoneill/redhat-ai-workflow/rebase-prgit clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflowWrote 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/dmzoneill/redhat-ai-workflow/rebase-pr)<a href="https://agentmods.dev/commands/dmzoneill/redhat-ai-workflow/rebase-pr"><img src="https://agentmods.dev/badge/commands/dmzoneill/redhat-ai-workflow/rebase-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.00000 | $0.00595 |
| Opus 5 | $0.00000 | $0.00298 |
| Sonnet 5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
rebase-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rebase-pr
Rebase a merge request onto latest main.
Overview
Rebase a merge request onto latest main.
Underlying Skill: rebase_pr
This command is a wrapper that calls the rebase_pr skill. For detailed process information, see skills/rebase_pr.md.
Arguments
| Argument | Required | Description |
|---|---|---|
mr_id |
No | - |
Usage
Examples
skill_run("rebase_pr", '{"mr_id": $MR_ID}')
# Rebase an MR
skill_run("rebase_pr", '{"mr_id": 1234}')
# Rebase onto different branch
skill_run("rebase_pr", '{"mr_id": 1234, "target_branch": "release-1.0"}')
Process Flow
This command invokes the rebase_pr skill. The process flow is:
flowchart LR
START([User runs /rebase-pr]) --> VALIDATE[Validate Arguments]
VALIDATE --> CALL[Call rebase_pr skill]
CALL --> EXECUTE[Execute Skill Steps]
EXECUTE --> RESULT[Return Result]
RESULT --> END([Complete])
style START fill:#6366f1,stroke:#4f46e5,color:#fff
style END fill:#10b981,stroke:#059669,color:#fff
style CALL fill:#3b82f6,stroke:#2563eb,color:#fff
```text
For detailed step-by-step process, see the [rebase_pr skill documentation](../skills/rebase_pr.md).
## Details
## Instructions
```text
skill_run("rebase_pr", '{"mr_id": $MR_ID}')
What It Does
- Gets MR details and source branch
- Fetches latest from origin
- Checks out the branch
- Rebases onto main
- Force pushes the rebased branch
Options
| Parameter | Description | Default |
|---|---|---|
mr_id |
MR ID to rebase | Required |
project |
GitLab project | Current repo |
target_branch |
Branch to rebase onto | main |
Additional Examples
# Rebase an MR
skill_run("rebase_pr", '{"mr_id": 1234}')
# Rebase onto different branch
skill_run("rebase_pr", '{"mr_id": 1234, "target_branch": "release-1.0"}')
Conflict Resolution
If conflicts occur, the skill will:
- Show conflicting files
- Wait for manual resolution
- Continue rebase after you fix conflicts
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.
- 4d ago First seen · 99 lines · 0 tokens per session scan A 27dd76b8ad6e
rebase-pr is a command published in the GitHub repository dmzoneill/redhat-ai-workflow (5 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 595 tokens. 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-31.
Other commands, from other repositories
pr-address
Address PR review comments on current branch.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
spec-research
需求 → 约束集（并行探索 + OPSX 提案）.
slack-gif-creator
Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".