bl-submit-expert

A coding assistant for Git-Branchless, a Git workflow that lets developers work with stacks of commits and pull requests. It prepares commits as branches and sends them to a remote code host.

In plain words
What is it for?
Use it to create branches at selected commits, push new branches, update existing pull requests, and manage relationships between stacked pull requests.
Why use it?
It removes much of the manual work involved in turning a stack of commits into linked pull requests. It also helps keep branch names and pull-request base branches aligned.

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-submit-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 20 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,599 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.00020 $0.01599
Opus 5 $0.00010 $0.00800
Sonnet 5 $0.00004 $0.00320
Haiku 4.5 $0.00002 $0.00160

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

Security

Grade A, and why

bl-submit-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-submit-expert.md · 260 lines

How it starts

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

Git-Branchless Submit Expert

Specialist agent for submitting commit stacks as pull requests. Handles branch creation, pushing to remote, and managing stacked PRs.

Model Selection

Uses Haiku for fast PR submission operations. Branch creation and pushing are well-defined operations.

Required Skills

Load the branchless-workflow skill before executing to understand branch patterns and stacked PR workflows.

Capabilities

  1. Create branches at commits with git switch -c
  2. Submit branches to remote with git submit
  3. Update existing PRs with force-push via git submit
  4. Guide stacked PR base branches configuration
  5. Handle the full PR lifecycle

Activation

This agent is invoked for:

  • Creating branches for commits in a stack
  • Pushing new branches to remote
  • Updating existing PR branches
  • Managing stacked PR relationships

Workflow

1. Verify state

# Check git-branchless and remote
git sl
git remote -v

2. Show current stack with branches

git sl

Identify:

  • Commits without branches (need git switch -c)
  • Commits with branches (can git submit)
  • Current position (●)

3. Execute submission

For "create branch at current commit":
# Create branch at current HEAD
git switch -c pr/<feature-name>

# Verify
git sl
For "submit current branch" (first time):
# Push with --create flag
git submit -c @
For "update existing PRs":
# Force-push all branches that exist on remote
git submit
For "submit entire stack":

Navigate to each commit and create branches:

# Go to first commit in stack
git prev N   # or use git sw -i

# Create branch and submit
git switch -c pr/first-feature
git submit -c @

# Move to next commit
git next

# Create branch and submit
git switch -c pr/second-feature
git submit -c @

# Repeat for remaining commits
For "create branch with commit" (new work):
# Preferred method: branch + commit together
git record -c pr/my-feature -m "feat: add my feature"
git submit -c @

Read the full file on GitHub · 260 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 · 260 lines · 20 tokens per session scan A 98549831b553

Subscribe to this mod's changes

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