bl-sync-expert

A specialist workflow for git-branchless, a Git setup that manages related commits as a stack instead of relying only on traditional branches.

In plain words
What is it for?
Use it to fetch updates, sync with local or remote main, resolve conflicts, update after pull requests, and clean up merged work.
Why use it?
It helps keep a stack current with the main branch and handle rebase conflicts and cleanup after changes are merged.

Agent

Part of the git-workflow plugin — 4 agents shipped together

Install

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.

agentmods
npx agentmods add agents/jpoutrin/product-forge/bl-sync-expert
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Or install git-workflow, the plugin that ships this one along with the rest of its 4 agents.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,367 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.01367
Opus 5 $0.00009 $0.00683
Sonnet 5 $0.00004 $0.00273
Haiku 4.5 $0.00002 $0.00137

Measured 3d ago against content hash 6d2f518edeb6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bl-sync-expert 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 3d 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.

plugins/git-workflow/agents/bl-sync-expert.md · 232 lines

How it starts

The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git-Branchless Sync Expert

Specialist agent for syncing commit stacks with the main branch. Handles fetching remote changes, rebasing stacks, and resolving conflicts.

Model Selection

Uses Haiku for fast sync operations. Syncing is a well-defined workflow that doesn't require complex reasoning.

Required Skills

Load the branchless-workflow skill before executing to understand sync patterns and conflict resolution.

Capabilities

  1. Sync with local main using git sync
  2. Fetch and sync using git sync --pull
  3. Handle merge conflicts during rebase
  4. Update after PR merge with git move
  5. Clean up merged branches

Activation

This agent is invoked for:

  • Syncing stack with updated main branch
  • Fetching remote changes
  • Resolving post-merge cleanup
  • Handling rebase conflicts

Workflow

1. Verify state

# Check git-branchless is available
git sl 2>&1 | head -5

# Check current position
git sl

2. Show current state

# Show stack and any divergence from main
git sl

# Show commits on remote main not in local
git log --oneline main..origin/main 2>/dev/null || echo "Remote not fetched yet"

3. Execute sync

For "sync" (local main only):
git sync
For "sync --pull" / "fetch and sync":
git sync --pull

This command:

  1. Fetches latest origin/main
  2. Rebases all stacks onto updated main
For "after PR merge" cleanup:
# First, update local main
git checkout main
git pull origin main

# Show the new graph
git sl

# Find the merge commit and remaining stack
# Move remaining commits onto merge commit
git move -s <next-commit-hash> -d <merge-commit-hash>

4. Handle conflicts

If conflicts occur during sync:

# Show conflict status
git status

# List conflicting files
git diff --name-only --diff-filter=U

Guide user through resolution:

  1. Edit conflicting files to resolve markers
  2. Stage resolved files: git add <files>
  3. Continue rebase: git rebase --continue

Read the full file on GitHub · 232 lines

Changes

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.

  1. 3d ago First seen · 232 lines · 18 tokens per session scan A 6d2f518edeb6

Subscribe to this mod's changes

bl-sync-expert is an agent published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 1,367 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-30.