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 tuwulalo/git-sync-check --skill git-sync-checkgit clone --depth 1 https://github.com/tuwulalo/git-sync-checkWrote 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/tuwulalo/git-sync-check/git-sync-check)<a href="https://agentmods.dev/skills/tuwulalo/git-sync-check/git-sync-check"><img src="https://agentmods.dev/badge/skills/tuwulalo/git-sync-check/git-sync-check/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/tuwulalo/git-sync-check/git-sync-check"><img src="https://agentmods.dev/badge/skills/tuwulalo/git-sync-check/git-sync-check.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.00153 | $0.01610 |
| Opus 5.5 | $0.00061 | $0.00644 |
| Sonnet 5.5 | $0.00031 | $0.00322 |
| Haiku 4.5 | $0.00015 | $0.00161 |
Grade A, and why
git-sync-check 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 1mo 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git sync pre-flight check
Several writers can touch the same working tree at once: the user, this session, and often a second Claude session that commits, builds and deploys in parallel. Your memory of the tree is stale the moment another writer acts. The point of this check is to learn the CURRENT state before you act on an outdated picture of it.
If the status is already in context
This skill ships with companion pre-flight scripts (see the repo README)
that many setups run automatically before each turn, injecting a
[git-sync] ... block into context. If you can see a fresh [git-sync]
line for the current prompt, do NOT re-run the commands — the snapshot is
already in front of you. Jump straight to the decision matrix and act on it.
The check
Run this before the first file edit of the task (one tool call):
git -C <repo> fetch origin --quiet
git -C <repo> status --short
git -C <repo> rev-list --left-right --count HEAD...origin/<default-branch>
When the default branch is unknown, resolve it first (falls back to
main):
git -C <repo> symbolic-ref --short refs/remotes/origin/HEAD
Three signals come back: dirty files, ahead count (left), behind count (right).
Decision matrix
| State | What to do |
|---|---|
| Clean tree, 0 ahead / 0 behind | Proceed. Report at most one line: ✅ git: чисто, синхронизировано |
| Behind, tree clean | git pull --rebase origin <branch>, then proceed |
| Ahead only | Note the unpushed commits. If they are complete work, push; if they look mid-flight (another session may still be working), leave them and say so |
| Dirty files | Classify them first — see below. Never blindly commit or revert |
| Dirty AND behind | Classify first, then follow the playbook below |
Operation in progress (.git/MERGE_HEAD, .git/rebase-merge/, .git/rebase-apply/, CHERRY_PICK_HEAD) |
STOP. Someone is mid-merge/rebase. Don't edit, don't commit, don't git rebase --abort on your own initiative — report it and wait for instructions |
Detached HEAD (git symbolic-ref HEAD fails) |
Don't commit onto it silently — a commit there is one GC away from being lost. Create/checkout a branch first, or ask which branch the work belongs on |
What ships with it
6 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.
- 1mo ago First seen · 131 lines · 0 tokens per session scan A 718cd028387b
git-sync-check is a skill published in the GitHub repository tuwulalo/git-sync-check (5 stars, last pushed 4mo ago), licensed MIT. It adds 153 tokens to every session and 1,610 once invoked, about $0.0006 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
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.
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.
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.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…