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 SII-Holos/synergy --skill git-guidegit clone --depth 1 https://github.com/SII-Holos/synergyWrote 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/sii-holos/synergy/git-guide)<a href="https://agentmods.dev/skills/sii-holos/synergy/git-guide"><img src="https://agentmods.dev/badge/skills/sii-holos/synergy/git-guide/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/sii-holos/synergy/git-guide"><img src="https://agentmods.dev/badge/skills/sii-holos/synergy/git-guide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00089 | $0.00811 |
| Opus 5.5 | $0.00036 | $0.00324 |
| Sonnet 5.5 | $0.00018 | $0.00162 |
| Haiku 4.5 | $0.00009 | $0.00081 |
Grade A, and why
git-guide 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 5d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Guide for Synergy Development
Inspect status, current branch and worktree ownership before editing or any Git mutation. Direct edits are allowed; preserve unrelated dirty and untracked files. Reuse an existing task worktree when it owns the branch. Do not switch or rebase a shared or pre-existing checkout without the user's explicit request. Do not stash, reset or clean shared work to move your changes.
Stage, commit, push, create a PR or mutate external systems only when the user requests that action. Do not use destructive Git commands, force pushes or hook bypasses without explicit authority and a reviewed recovery plan. Amend only your own unpushed task commit when requested or a hook modified intended content; never rewrite someone else's work.
Every agent-created commit ends with:
Co-authored-by: synergy-agent <[email protected]>
Protect Branches and Scope
- Never push directly to the protected
devormainbranches. - Local commits on
devormainare permitted when the user requests them, but they advance a potentially shared branch. Publish through a topic branch and open a pull request againstdev. - The release workflow is the only path from
devtomain. - Inspect
git statusbefore editing, staging, committing, rebasing, or publishing. - Preserve unrelated dirty and untracked files. Stage only explicit files owned by the current task.
Keep Internal Data Out of Outbound Text
Never expose the following in a commit message, pull-request body, issue/PR comment, or review:
| Category | Forbidden content |
|---|---|
| Local filesystem paths | absolute home/project paths or home-relative checkout paths |
| Synergy runtime paths | .synergy homes, temporary runtime/worktree locations, or SYNERGY_HOME values |
| Session and Scope identity | session IDs, Scope IDs, or equivalent internal identifiers |
| Logs and diagnostics | local log paths, raw logs, traces, and diagnostic artifacts |
| Credentials | auth/config-store paths, API keys, tokens, secrets, or secret-like values |
| Internal configuration | provider endpoints, MCP addresses, private service URLs, or equivalent deployment details |
What ships with it
4 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.
- 5d ago Changed · -131 lines b280b3cb89f9
- 12d ago Changed · +2 lines e979e536243d
- 14d ago Changed · +2 lines bb81b9775a87
- 21d ago Changed · +1 lines 2bd7b750785c
- 24d ago Changed aea0f0674c52
- 27d ago Changed · +2 lines 602994dd6c4c
- 1mo ago Changed · +1 lines f7dd5204a400
- 1mo ago Changed · +2 lines c4426fc59f6c
- 1mo ago Changed · +3 lines 81d8d6a4de85
- 1mo ago First seen · 173 lines · 89 tokens per session scan A fd79a8b10ee3
git-guide is a skill published in the GitHub repository SII-Holos/synergy (388 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 811 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.