syncing-branch-with-base

syncing-branch-with-base is a skill for Claude Code, Codex from Muriel-Salvan/x_aeon_agents. It costs 110 tokens per session (984 once invoked), scanned A, original, BSD-3-Clause.

A guide for updating a coding branch from its base branch. A branch is a separate line of code changes, while the base branch is the branch it started from.

In plain words
What is it for?
It is for checking the remote base branch, rebasing the current branch onto it, and pushing the updated branch back to the remote.
Why use it?
It helps account for changes made to the base branch so the current work is brought up to date before it is shared.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for checking the remote base branch, rebasing the current branch onto it, and pushing the updated branch back to the remote.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/muriel-salvan/x_aeon_agents/syncing-branch-with-base
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.

Any agent
npx skills add Muriel-Salvan/x_aeon_agents --skill syncing-branch-with-base
Clone the repo
git clone --depth 1 https://github.com/Muriel-Salvan/x_aeon_agents

Made for: Claude Code, Codex.

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.

agentmods badge for syncing-branch-with-base

README.md
[![agentmods](https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/syncing-branch-with-base/github.svg)](https://agentmods.dev/skills/muriel-salvan/x_aeon_agents/syncing-branch-with-base)
Your own site
<a href="https://agentmods.dev/skills/muriel-salvan/x_aeon_agents/syncing-branch-with-base"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/syncing-branch-with-base/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.

agentmods 80×15 button for syncing-branch-with-base

Your own site · 80×15
<a href="https://agentmods.dev/skills/muriel-salvan/x_aeon_agents/syncing-branch-with-base"><img src="https://agentmods.dev/badge/skills/muriel-salvan/x_aeon_agents/syncing-branch-with-base.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 984 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00110 $0.00984
Opus 5.5 $0.00044 $0.00394
Sonnet 5.5 $0.00022 $0.00197
Haiku 4.5 $0.00011 $0.00098

Measured 2mo ago against content hash da1128ad297a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

syncing-branch-with-base 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 2mo 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.

skills/syncing-branch-with-base/SKILL.md · 110 lines

How it starts

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

Syncing the current branch with its base

Sequential steps to be followed when using this skill

When syncing the current branch with its base, follow those steps.

Create the syncing-branch-with-base Execution Checklist (MANDATORY)

  • Before executing anything, create a checklist named syncing-branch-with-base Execution Checklist with all steps of these instructions.
  • The syncing-branch-with-base Execution Checklist must include all numbered steps explicitly.
  • After completing each step of these instructions, mark the item in the syncing-branch-with-base Execution Checklist as completed.
  • Do not skip any item.
  • If an item cannot be executed, explicitly explain why.
  • Never mark the task as completed while any item from the syncing-branch-with-base Execution Checklist remains open.

1. Inform the user

  • Always tell the user "SKILL: I am syncing the current branch with its base" to inform the user that you are running this skill.

2. Find the base branch name

  • By default the base branch name is main.
  • The base branch name is later referenced as {base_branch}.

3. Fetch the base branch from the github remote

  • Always use cli: git fetch --all to retrieve the GitHub remote's base branch.

Example:

git fetch --all

4. Rebase the branch

  • Always use cli: git rebase github/{base_branch} to bring your branch on top of its base as on the GitHub remote.
  • Never use cli: git merge.
  • Always fix any conflict you see during the rebase, and continue the rebase using cli: git rebase --continue until all your commits have been rebased properly.
  • If you don't know how to solve a conflict, then always use agent: ask_followup_question to ask the user to help you solve the git conflict.

Example:

git rebase github/main
# Fix potential conflicts in files
git rebase --continue
# Use agent tool ask_followup_question about new potential conflicts that you don't understand how to solve
git rebase --continue

5. Push the rebased branch

Read the full file on GitHub · 110 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. 2mo ago First seen · 110 lines · 110 tokens per session scan A da1128ad297a

Subscribe to this mod's changes

syncing-branch-with-base is a skill published in the GitHub repository Muriel-Salvan/x_aeon_agents (2 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 110 tokens to every session and 984 once invoked, about $0.0004 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-31.