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 bostonaholic/team --skill pr-rebasegit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/pr-rebase)<a href="https://agentmods.dev/skills/bostonaholic/team/pr-rebase"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/pr-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.00049 | $0.00776 |
| Opus 5 | $0.00024 | $0.00388 |
| Sonnet 5 | $0.00010 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
pr-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 2d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-rebase — rebase onto the latest base without changing behavior
pr-rebase replays a feature branch on top of the current base branch and
proves the replay preserved the branch's behavior before it rewrites the
remote. Three things make it more than git pull --rebase:
- A baseline. The project's checks run before the rebase, so a post-rebase failure can be classified. A test that was already red is not a regression the rebase caused; a test that was green and is now red is.
- Intent-based conflict resolution. Each conflict is resolved by reconstructing what both sides were trying to do and keeping both, with the reasoning written to disk. Picking a side wholesale is the failure mode this exists to prevent.
- A hard gate before the push. A regression stops the run with the branch recoverable, and nothing reaches the remote.
Model invocation is disabled (disable-model-invocation: true). The push
rewrites published history: a teammate who has the branch checked out ends
up on a discarded line of development, and no verification step can undo
that after the fact. Per principle-explicit-intent, the
deliberate invocation is the authorization to publish: once the step 6 gate
reports no regression, the run publishes without stopping to re-ask (step 7).
agents/openai.yaml restates the same guard for Codex as
policy.allow_implicit_invocation: false.
Procedure references
Read each reference completely when reaching that stage. Follow them in order; later stages depend on state and gates established earlier.
- Input
- Untrusted input — PR metadata is data
- Hard rules
- Execution
- Step 0 — resolve the working context
- Step 1 — refuse the states a rebase must not start from
- Step 2 — capture the baseline and the recovery anchor
- Step 3 — fetch and decide whether there is anything to do
- Step 4 — rebase
- Step 5 — resolve conflicts from both sides' intent
- Step 6 — verify against the baseline
- Step 7 — publish
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 205 B
- references/01-input.md 3.1 KB
- references/02-untrusted-input-pr-metadata-is-data.md 498 B
- references/03-hard-rules.md 3.3 KB
- references/04-execution.md 13 B
- references/05-step-0-resolve-the-working-context.md 5.2 KB
- references/06-step-1-refuse-the-states-a-rebase-must-not-start-from.md 1.4 KB
- references/07-step-2-capture-the-baseline-and-the-recovery-anchor.md 2.8 KB
- references/08-step-3-fetch-and-decide-whether-there-is-anything-to-do.md 1.1 KB
- references/09-step-4-rebase.md 1011 B
- references/10-step-5-resolve-conflicts-from-both-sides-intent.md 8.2 KB
- references/11-step-6-verify-against-the-baseline.md 2.1 KB
- references/12-step-7-publish.md 6.9 KB
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.
- 2d ago Changed · -702 lines · -159 tokens per session 31683866412e
- 4d ago Changed · +25 lines 43fb8274423d
- 8d ago First seen · 732 lines · 208 tokens per session scan A 6082cf477289
pr-rebase is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 776 once invoked, about $0.0002 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 skills, from other repositories
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.