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 lugassawan/swe-workbench --skill workflow-branch-syncgit clone --depth 1 https://github.com/lugassawan/swe-workbenchWrote 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/lugassawan/swe-workbench/workflow-branch-sync)<a href="https://agentmods.dev/skills/lugassawan/swe-workbench/workflow-branch-sync"><img src="https://agentmods.dev/badge/skills/lugassawan/swe-workbench/workflow-branch-sync/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/lugassawan/swe-workbench/workflow-branch-sync"><img src="https://agentmods.dev/badge/skills/lugassawan/swe-workbench/workflow-branch-sync.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.00055 | $0.07474 |
| Opus 5.5 | $0.00022 | $0.02990 |
| Sonnet 5.5 | $0.00011 | $0.01495 |
| Haiku 4.5 | $0.00006 | $0.00747 |
Grade A, and why
workflow-branch-sync 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 16d 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Branch Sync
Announce at start: "I'm using the workflow-branch-sync skill to bring this branch up to date and help resolve any conflicts."
When to Invoke
- User's branch has fallen behind the default branch and they want it brought up to date.
- User asks for help resolving merge/rebase conflicts, or wants guidance on "which side is correct".
- Invoked by
/swe-workbench:sync.
What This Skill Does NOT Do
- Does not open, merge, or comment on a PR — that is
swe-workbench:workflow-commit-and-pr/ the user's action. Sole exception: Step 7.5 may trim provably-stale scope tags from the open PR's title (reported in the summary) — never pushes, comments, or merges. - Does not resolve any conflict without first showing both sides and a recommendation with rationale.
- Does not auto-push — ever. The push is a separate, explicitly prompted step at the end.
- Does not rewrite history beyond the single merge or rebase the user asked for.
Sync Contract
Step 1 — Preflight Guard
command -v swe-workbench-skill-script >/dev/null 2>&1 || {
echo "swe-workbench runtime commands not on PATH — reinstall or update the swe-workbench plugin." >&2
exit 1
}
eval "$(swe-workbench-skill-script workflow-branch-sync preflight-guard.sh)"
Emits CURRENT_BRANCH, DEFAULT_BRANCH (detected — never hardcode main), IS_DEFAULT, DETACHED, DIRTY.
IS_DEFAULT=1: refuse. Report "already on$DEFAULT_BRANCH— nothing to sync onto itself" and stop.DETACHED=1: refuse. Report "detached HEAD — checkout a branch first" and stop.DIRTY>0: offer stash-or-abort before touching history —git stash push -u -m "branch-sync: pre-sync stash"if the user opts to stash, otherwise stop and let the user commit or discard first. Never proceed with a dirty tree. If the user stashes, setSTASHED=1— Step 8 restores it before reporting.
Step 1.5 — Refresh Remote Refs
Never compare against a locally-cached origin/$DEFAULT_BRANCH — the sync decision is only as fresh as that ref. Before any advisory, capture, or mechanical sync runs:
What ships with it
5 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.
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.
- 16d ago Changed · +19 lines 458b708754dc
- 17d ago Changed · +13 lines 4f3fb762ef7d
- 24d ago Changed · +24 lines 65cd6676f473
- 1mo ago First seen · 209 lines · 55 tokens per session scan A 22721e1631e2
workflow-branch-sync is a skill published in the GitHub repository lugassawan/swe-workbench (3 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 7,474 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.
update-pr
Update an existing pull request with new changes. Use when the user wants to update a PR, push follow-up changes to a PR, refresh a PR description, or sync a PR with latest commits. Triggers on: update pr, update-pr, update the pr, push to pr, refresh pr, sync pr, update pull request.
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — no skill executes…
architecture-refiner
Facilitate a structured conversation to define architecture principles for a repository. Supports multiple architecture styles: clean architecture (default), hexagonal / ports & adapters, modular monolith, or custom. Produces a formal architecture document that the corresponding atom will use. Use when setting up a…