A workflow for pushing the current Git branch to the shared remote repository called origin. It also sets the branch’s upstream connection when needed.

Handle requests such as “push my branch” or “get my branch onto GitHub.” It covers the push step before opening a pull request.

It puts your local commits on the remote repository so others can access the branch and a pull request can be opened afterward.

How egregore-labs/egregore configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to egregore-labs/egregore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/push/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/egregore-labs/egregore

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/egregore-labs/egregore/push.svg)](https://agentmods.dev/skills/egregore-labs/egregore/push)

Your own site

<a href="https://agentmods.dev/skills/egregore-labs/egregore/push"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/push.svg" alt="Measured on agentmods" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 820 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00035	$0.00820
Opus 5	$0.00017	$0.00410
Sonnet 5	$0.00007	$0.00164
Haiku 4.5	$0.00003	$0.00082

Measured 2d ago against content hash e9d2395ef072, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

push 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.

.claude/skills/push/SKILL.md · 66 lines

How it starts

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

Push current branch to remote.

When to invoke

User says: "/push", "push my branch", "push this up", "get my branch onto GitHub", or needs the current branch pushed to origin before opening a PR. Not this: ready to open the PR itself → /pr (run after push).

Loom routing

Skip this section if your prompt contains LOOM-EXECUTOR — you are the executor; run the skill as specced below. Full protocol: .claude/context/loom.md.

Resolve: ROUTE=$(bash bin/loom.sh route push), then DECISION_ID=$(printf '%s\n' "$ROUTE" | jq -r '.decision_id // empty').
If mode ≠ delegate, or the user signalled depth ("deep", "think hard", --deep) → run this skill inline as normal. On a depth override, print bash bin/loom.sh footer push --override after the output and set "override":true in telemetry.
Otherwise delegate: spawn the Agent tool with subagent_type: "loom-executor", model = the route's tier, prompt = LOOM-DECISION-ID: $DECISION_ID on its own first line, then LOOM-EXECUTOR: Execute .claude/skills/push/SKILL.md, plus the user's arguments and any context the spec needs from the session. Print the executor's final output verbatim, then print the output of bash bin/loom.sh footer push.
If the spawn fails or the executor's first line is LOW_CONFIDENCE: — triage the reason: needs-user-interaction or a main-loop-only tool → take over and finish this skill inline (no escalation); genuine uncertainty or failure → reassign ROUTE=$(bash bin/loom.sh escalate push "<reason>"), refresh DECISION_ID from ROUTE, then re-spawn once on the new tier carrying the returned decision ID (sticky for this session).
Telemetry (fire-and-forget): bash bin/telemetry.sh emit "command" '{"command":"push","routed":true,"mode":"delegate","model":"<actual>","route_tier":"<table tier>","class":"<class>","escalated":<bool>,"override":<bool>,"source":"<source>"}' 2>/dev/null &

Before anything else

Resolve BASE_BRANCH through bin/lib/config.sh → _get_base_branch (pass the managed repo name when applicable). Check git branch --show-current. If on a protected branch ($BASE_BRANCH, develop, main, or master): → Use the resolved base branch (default "develop") → Create a working branch: git fetch origin $BASE_BRANCH --quiet && git checkout --no-track -b dev/{author}/{topic-slug} origin/$BASE_BRANCH → Tell the user: "Creating a working branch for this..." — never mention git commands to the user. → Then proceed with the push.

Read the full file on GitHub · 66 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.

2d ago Changed e9d2395ef072
7d ago First seen · 66 lines · 35 tokens per session scan A 8ee2cc5a28ba

Subscribe to this mod's changes

push is a skill published in the GitHub repository egregore-labs/egregore (282 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 820 once invoked, about $0.0002 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.

Claude Code Collaboration Git and workflow ai claude cli developer-tools

gwm

Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…

kbrdn1/gwm-cli · 0 tokens

agentplane

Use when a repository uses AgentPlane or the user wants a governed git-native workflow for planning, task execution, verification, and closure.

basilisk-labs/agentplane · 30 tokens

aigon-next

Suggest the most likely next workflow action based on current context.

jayvee/aigon · 15 tokens

release

Release Aigon — push to origin, cut a version+tag, or publish to npm. Wraps scripts/ship.js with CHANGELOG draft + dry-run preview. Triggers when the user types "/release", "/push", "/ship", or says "ship a release", "publish a beta", "cut a version", "push to origin", "release X to npm".

jayvee/aigon · 79 tokens

aigon-feature-transfer

Transfer feature from its current agent to a different agent — preserves commits and in-flight work.

jayvee/aigon · 25 tokens

take-task

A workflow for claiming a tracker task and preparing the development branch for it. It verifies the task, marks it as in progress, checks for uncommitted changes, and handles branch setup according to the task state.

restarter/lets-workflow · 76 tokens

egregore: Skill for Claude Code