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 ronaknnathani/relay --skill rebasegit clone --depth 1 https://github.com/ronaknnathani/relayWrote 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/ronaknnathani/relay/rebase)<a href="https://agentmods.dev/skills/ronaknnathani/relay/rebase"><img src="https://agentmods.dev/badge/skills/ronaknnathani/relay/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.1 | $0.00024 | $0.00688 |
| Opus 5 | $0.00012 | $0.00344 |
| Sonnet 5 | $0.00005 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
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 7d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rebase — Rebase, Fix Conflicts, Push
Rebase the current branch onto the base branch (default: main), resolve any merge conflicts, and force-push.
Steps
1. Determine Base Branch
- If
$ARGUMENTScontains a branch name, use it as the base. - Otherwise, default to
main.
2. Pre-check Working Tree
git status --porcelain
If output is non-empty, the working tree is dirty. Abort and report to the user:
Working tree has uncommitted changes. Commit or stash before rebasing:
<output of git status --porcelain>
Do NOT auto-stash — too easy to lose work.
3. Fetch Latest
git fetch origin <BASE_BRANCH>
4. Rebase
git rebase origin/<BASE_BRANCH>
5. Handle Conflicts
If the rebase stops with conflicts:
- Run
git diff --name-only --diff-filter=Uto list conflicted files - For each conflicted file:
- Read the file to understand the conflict markers
- Resolve the conflict by understanding both sides (ours = current branch work, theirs = base branch changes)
- Prefer keeping our changes where they don't conflict with upstream intent
- If unsure about a conflict, ask the user
- Stage the resolved files:
git add <resolved-files> - Continue the rebase:
git rebase --continue - If more conflicts appear, repeat steps 1-4
- Max 10 conflict rounds — if still conflicting, abort and ask the user
6. Verify
After successful rebase:
git log --oneline -5
7. Push
Check whether the branch has an upstream:
git rev-parse --abbrev-ref --symbolic-full-name @{upstream} 2>/dev/null
- If the command fails (no upstream): the branch has never been pushed. Use:
git push -u origin "$(git rev-parse --abbrev-ref HEAD)" - If the command succeeds: check ahead/behind state:
ahead=$(git rev-list --count @{upstream}..HEAD) behind=$(git rev-list --count HEAD..@{upstream})- If both
ahead == 0andbehind == 0: nothing to push, skip. - Otherwise (ahead, behind, or diverged):
git push --force-with-lease
- If both
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.
- 7d ago First seen · 98 lines · 24 tokens per session scan A c4354cc66089
rebase is a skill published in the GitHub repository ronaknnathani/relay (3 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 688 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 skills, from other repositories
conventional-commit
Generer conventional commit-meldinger med Nav-relevante scopes og breaking change-format.
repo-status
Checks the status of the repository.
repo-status
Checks the status of the repository.
git-ops
Safe git operations including commits, branches, merges, worktrees, and conflict resolution. Use when user wants to commit and push changes, manage branches, resolve conflicts, or create isolated workspaces. Activates when user says "commit", "push", "merge", "branch", "pull", "rebase", "worktree", "conflict", or…
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.