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 escapeboy/ai-prompts --skill git-sync-branchesgit clone --depth 1 https://github.com/escapeboy/ai-promptsWrote 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/escapeboy/ai-prompts/git-sync-branches)<a href="https://agentmods.dev/skills/escapeboy/ai-prompts/git-sync-branches"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/git-sync-branches/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/escapeboy/ai-prompts/git-sync-branches"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/git-sync-branches.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.01946 |
| Opus 5.5 | $0.00032 | $0.00778 |
| Sonnet 5.5 | $0.00016 | $0.00389 |
| Haiku 4.5 | $0.00008 | $0.00195 |
Grade A, and why
git-sync-branches 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 14d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-sync-branches
Commit everything, merge finished feature branches into develop, sync master/main, delete merged and Close branches. Handles submodules.
When to Use (and When NOT to)
| Use this skill for | Use a simpler approach for |
|---|---|
| Cleaning up multiple stale feature branches across a repo (and submodules) into develop/master | Merging a single branch you're actively working on — just git merge <branch> |
| Bulk local + remote branch deletion after a sprint/release | Deleting one branch you already know is safe — git branch -d <branch> |
| Repos with git submodules needing coordinated branch sync | Single-repo, no-submodule projects — plain git merge + git push |
| Restoring master/develop to a known-clean, in-sync state | Reviewing a PR before merge — use the code-review skill instead |
Workflow
Step 1: Commit uncommitted changes
git status
If there are untracked files or modifications, commit them:
git add <specific files or dirs>
git commit -m "chore: commit pending changes before branch sync"
Step 2: Identify the main branch name
- Check for
mastervsmain— use whichever exists - Check for
develop— this is the integration branch
git branch | grep -E "^\*? *(master|main|develop)$"
Step 3: Process submodules (if any)
For each git submodule, run the full sync workflow inside the submodule first:
git submodule status
For each submodule that has feature branches:
cd <submodule-path>- Run Steps 1–12 of this workflow inside the submodule (its own
develop→main, deletions and push) cd ..back to parent
Step 4: Find all feature branches ahead of develop
git branch | grep "feat/"
For each feature branch, check how many commits it's ahead of develop:
git log --oneline develop..<branch> | wc -l
Only merge branches that are actually ahead (non-zero).
Step 4b: Triage each branch — merge, hold, or close (don't blanket-merge)
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.
- 14d ago Changed · +21 lines · +19 tokens per session 2721d6dc25ec
- 27d ago Changed · +15 lines 1def3853dbe9
- 1mo ago First seen · 173 lines · 61 tokens per session scan A 3c6032a3e04f
git-sync-branches is a skill published in the GitHub repository escapeboy/ai-prompts (91 stars, last pushed 15d ago), licensed MIT. It adds 80 tokens to every session and 1,946 once invoked, about $0.0003 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.