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 Muriel-Salvan/x_aeon_agents --skill syncing-branch-with-basegit clone --depth 1 https://github.com/Muriel-Salvan/x_aeon_agentsWrote 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/muriel-salvan/x_aeon_agents/syncing-branch-with-base)<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.
<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>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.00110 | $0.00984 |
| Opus 5.5 | $0.00044 | $0.00394 |
| Sonnet 5.5 | $0.00022 | $0.00197 |
| Haiku 4.5 | $0.00011 | $0.00098 |
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.
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 --allto 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 --continueuntil all your commits have been rebased properly. - If you don't know how to solve a conflict, then always use
agent: ask_followup_questionto 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
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.
- 2mo ago First seen · 110 lines · 110 tokens per session scan A da1128ad297a
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.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.