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 RockyHong/super-bootstrap --skill mergegit clone --depth 1 https://github.com/RockyHong/super-bootstrapWrote 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/rockyhong/super-bootstrap/merge)<a href="https://agentmods.dev/skills/rockyhong/super-bootstrap/merge"><img src="https://agentmods.dev/badge/skills/rockyhong/super-bootstrap/merge/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rockyhong/super-bootstrap/merge"><img src="https://agentmods.dev/badge/skills/rockyhong/super-bootstrap/merge.svg" alt="Reviewed on agentmods" width="80" 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.00130 | $0.03309 |
| Opus 5.5 | $0.00052 | $0.01324 |
| Sonnet 5.5 | $0.00026 | $0.00662 |
| Haiku 4.5 | $0.00013 | $0.00331 |
Grade A, and why
merge 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
merge — Branch Absorption
Absorb feature branches into the base branch; several branches land as one batch (§ 5b). Conflict resolution is NOT this skill's job — abort, surface, stop. Regenerating derived output (§ 5b step 2) is not resolution: it takes no judgment.
Branch Absorption Lane (load-bearing)
Branch integration is a topology operation on the commit graph. Route through the merge tool — git merge, this skill, or worker-direct-merge. File extension is not a routing signal; a docs-only branch is still branch integration.
Pre-flight when integration is in scope
Triggers: branch named for absorption, current branch behind base, worker returned with branch unmerged.
git branch --no-merged <base>— list unmerged tips.- For any file slated for edit:
git log <base>..<branch> -- <path>. Non-empty → merge lane. - To inspect merge state, materialize it:
git merge --no-commit --no-ff <branch>, thengit merge --abort. Readgit diff <base>..<branch>for review only, never as input to a hand-applied edit across base.
Conflict Doctrine (load-bearing)
When git merge or git rebase stops with unmerged paths (git diff --name-only --diff-filter=U lists files):
- Abort immediately —
git merge --abort(for merge) orgit rebase --abort(for rebase). Restore the working tree. - Surface, don't resolve. Output the branch name, the conflict file list (the unmerged-path list above, captured BEFORE abort), and which strategy hit the conflict.
- Stop the run. Do not attempt resolution — resolution never runs inside this skill. The step-2 surface is the conflict scope. Route it: if the consuming repo's harness names a conflict-resolution agent (its CLAUDE.md or agent roster — e.g. a builder/implementer agent), offer dispatching that agent with the conflict scope and the § Resolver contract below as the recommended next step; otherwise the user resolves manually or re-dispatches with a different strategy.
This rule applies to every branch in the queue. If branch A conflicts, abort A, surface, then continue with branches B, C — they're independent attempts. Don't skip them silently.
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 · +41 lines · +73 tokens per session e9065ad649dd
- 28d ago Changed · -1 lines 7e721819373d
- 1mo ago Changed · -5 lines 7b10d356c802
- 1mo ago First seen · 127 lines · 57 tokens per session scan A e08680a92b29
merge is a skill published in the GitHub repository RockyHong/super-bootstrap (3 stars, last pushed today), licensed MIT. It adds 130 tokens to every session and 3,309 once invoked, about $0.0005 per session on Opus 5.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
github-pr-merge
Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
git-commit
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.
reissverschluss-merge
Reißverschluss-Verfahren (englisch: zipper merge) für sehr konfliktreiche Merges: Wenn zwei divergente Branches oder ein PR und sein Zielbranch BEIDE wertvolle, unvereinbar erscheinende Änderungen tragen, wird nicht pauschal eine Seite gewählt, sondern Abschnitt für Abschnitt verglichen, per Entscheidungstabelle…
git-advanced
A guide to advanced Git, the version-control system used to track code changes, including branches, rebasing, cherry-picking, and hooks.
qector-release-engineering
QECTOR release engineering, wheel-only distribution, the chunked base64 Rust-core delivery, feature flags in published wheels, the pre-flight gates, and the v2 token format. Load for any question about packaging, building, releasing, the RUSTSRCB64 secrets bundle, the promotion of a Provisional symbol to stable, or…