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/opsmill/infrahub-mcp/rebasegit clone --depth 1 https://github.com/opsmill/infrahub-mcpWrote 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/opsmill/infrahub-mcp/rebase)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/rebase"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/rebase.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.00019 | $0.01088 |
| Opus 5 | $0.00010 | $0.00544 |
| Sonnet 5 | $0.00004 | $0.00218 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
rebase 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rebase Branch
Introduction
Rebase the current branch onto the latest base branch, resolving any merge conflicts by preserving the intent of local changes. Optionally force-push and monitor CI status on GitHub.
Arguments
#$ARGUMENTS
Supported arguments:
push— After a successful rebase, force-push the branch upstream and monitor GitHub Actions CI until completion.
Main Tasks
1. Assess Current State
- Verify we are NOT on
stableormain:
If on a protected branch, stop immediately.git branch --show-current - Check for uncommitted changes:
If there are uncommitted changes, stop — rebase requires a clean working tree.git status --short - Determine the base branch (default:
stable):git log --oneline stable..HEAD | wc -l - Count local commits to know what to expect after rebase:
git log --oneline stable..HEAD
2. Update Base Branch & Rebase
- Fetch the latest remote state:
git fetch origin - Start the rebase:
git rebase origin/stable - If the rebase completes cleanly, skip to Phase 4.
3. Resolve Merge Conflicts
If conflicts occur:
- Identify conflicting files:
git diff --name-only --diff-filter=U - For each conflicting file:
- Read the file and understand both sides of the conflict
- Preserve local intent — our changes take priority since we're landing our work on top of the latest base
- Resolve the conflict, keeping the logic consistent
- Stage the resolved file:
git add <file>
- Continue the rebase:
git rebase --continue - Repeat until all conflicts are resolved.
When to ask the user:
- Both sides modify the same logic in incompatible ways
- A file was deleted on one side and modified on the other
- Merge markers appear in generated files
4. Verify Rebase Result
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 · 145 lines · 19 tokens per session scan A 418640db1a0e
rebase is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 1,088 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-31.
Other commands, from other repositories
cl
Audit changelog entries before release.
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.
AGENTS
Per-command agent-optimized usage and structure guide.
pre-commit
Run pre-commit checks identical to GitHub CI (ruff, mypy, tests).
/opsx-ff
Create a change and generate all artifacts needed for implementation in one go.