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 paultyng/skill-issue --skill rebase-pr-chaingit clone --depth 1 https://github.com/paultyng/skill-issueWrote 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/paultyng/skill-issue/rebase-pr-chain)<a href="https://agentmods.dev/skills/paultyng/skill-issue/rebase-pr-chain"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/rebase-pr-chain.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.00054 | $0.00639 |
| Opus 5 | $0.00027 | $0.00319 |
| Sonnet 5 | $0.00011 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
rebase-pr-chain 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 8d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rebase PR Chain
Rebase a chain of dependent PRs so they are all up-to-date and mergeable.
1. Identify the Chain
Accept PR numbers from the user, or detect the chain automatically:
gh pr list --state open --json number,baseRefName,headRefName
Build the dependency graph: each PR's baseRefName points to the branch of the PR it depends on. Sort topologically (base branch first).
If the user provides explicit PR numbers (e.g. "33, 34, 35, 36, 37"), use that order directly.
2. Rebase Each PR
For each PR in the chain (starting from the one closest to the trunk):
a. Fetch and checkout
git fetch origin <baseRefName> <headRefName>
git checkout <headRefName>
Verify the working tree is clean.
b. Rebase
git rebase origin/<baseRefName>
If the rebase completes cleanly, skip to step (d).
c. Resolve Conflicts
Follow the same conflict resolution strategy as fix-pr-conflict:
- List conflicting files:
git diff --name-only --diff-filter=U - For each file, understand both sides and classify:
- Mechanical: independent changes to nearby lines. Keep both.
- Semantic: incompatible changes to the same logic. Resolve if the outcome is clear.
- Ambiguous: design decisions or unclear intent. Abort the rebase (
git rebase --abort) and escalate to the user with a description of the conflict.
- After resolving:
git add <file>thengit rebase --continue - Repeat until the rebase completes or escalation is needed.
d. Verify
Run verification per verify-when-complete. Fix any issues from bad conflict resolution. If errors are unrelated, note them.
e. Force push
git push --force-with-lease
3. Verify Chain Mergeability
After all PRs are rebased, verify each is mergeable:
gh pr view <number> --json mergeable,mergeStateStatus
If GitHub still reports conflicts (recomputation delay), wait a few seconds and re-check once.
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.
- 8d ago First seen · 84 lines · 54 tokens per session scan A d7d2edcf083c
rebase-pr-chain is a skill published in the GitHub repository paultyng/skill-issue (9 stars, last pushed 28d ago), licensed MIT. It adds 54 tokens to every session and 639 once invoked, about $0.0003 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
gh-contribution-planner
Daily GitHub contribution planner — analyzes the gh-logged-in user's non-archived repos (owned + forks) and recent contributions, produces a prioritized plan, halts for approval, then dispatches parallel sub-agents to execute approved items via existing PR/CI/review skills.
swarm-handoff
Create artifact/commit file handoffs for Agent Toolkit swarms with worktree-per-writer, branch, and promotion integration.
fix-merge-conflicts
Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution.
worktree
Manage Git worktrees per writer for Agent Toolkit swarms — isolated branches, handoff promotion, and cleanup.
gh-address-comments
Triage and address open GitHub PR review and conversation comments using the gh CLI. Use when the user wants to "address PR comments", "resolve review threads", or "respond to reviewers" on the current branch's pull request.
project
Clone, index, and orchestrate multi-repo work via agent-toolkit project — symlinks, quick access, and swarm workspaces.