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 0x0w1/jig --skill github-syncgit clone --depth 1 https://github.com/0x0w1/jigWrote 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/0x0w1/jig/github-sync)<a href="https://agentmods.dev/skills/0x0w1/jig/github-sync"><img src="https://agentmods.dev/badge/skills/0x0w1/jig/github-sync/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/0x0w1/jig/github-sync"><img src="https://agentmods.dev/badge/skills/0x0w1/jig/github-sync.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.00063 | $0.03978 |
| Opus 5.5 | $0.00025 | $0.01591 |
| Sonnet 5.5 | $0.00013 | $0.00796 |
| Haiku 4.5 | $0.00006 | $0.00398 |
Grade A, and why
github-sync 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.
This is a copy
100% identical to jig-github-sync — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Sync
Use this repository skill only for setup and synchronization of GitHub repository settings.
Scope
- Branches:
main,develop. - Branch protection for
mainanddevelop: optional, and only when the repository can have it. jig guarantees exactly two things — force pushes blocked and deletion blocked — and adds nothing else. It does not require pull-request reviews or status checks, and not requiring them is not the same as removing them: a repository that already requires either keeps requiring it. See Branch Protection Is Optional. - Local guard, first layer: a git
pre-pushhook installed fromassets/pre-pushbyscripts/manage-pre-push.sh. It blocks force pushes to and deletion ofmain/developand restricts directmainpushes to the release fast-forward (develop:main) and the hotfix landing (hotfix/<slug>:main, owned byhotfix-flow). Local defense only; server-side protection stays the final barrier. - Local guard, second layer: the same policy as a
PreToolUsehook that inspects the push command before it runs,--no-verifyincluded, which a git hook cannot see. Claude Code runs it from inside thejigplugin. Codex does not run a plugin's own hooks, so Codex (.codex/hooks.json) and Antigravity (.agents/hooks.json) get the hook entry fromscripts/manage-native-hooks.shinstead. The manager copies the shippedassets/guard-push.shclone-local to<git common dir>/jig/guard-push.shand the entry runs that copy, so one entry works whether jig arrived as a plugin or as skill files. Project scope only — a user-scope entry would guard repositories jig is not installed in. - No release-drafter files, no pull request template, no label sync; the release flow is CLI-driven (
github-release) and does not use pull requests. - Sync is convergent and idempotent: one run aligns the repository with the current model even when several jig versions were skipped.
jig-updateruns it after updating installed files.
Branch Protection Is Optional
What ships with it
7 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 Changed · +34 lines 6d391fc9af51
- 1mo ago Changed · +1 lines c06e4c9feb01
- 1mo ago Changed · +14 lines · +15 tokens per session cda8dbe476d7
- 1mo ago First seen · 123 lines · 48 tokens per session scan A dffa1be562f5
github-sync is a skill published in the GitHub repository 0x0w1/jig (5 stars, last pushed 20d ago), licensed MIT. It adds 63 tokens to every session and 3,978 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to jig-github-sync, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
git-ship
An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.
worktree-pipeline-skill
Tracker-ticket-to-merged-PR pipeline via git worktrees — sync, plan, adaptive review, /run-plan, code review, PR merge. Triggers: run-worktree-pipeline, worktree pipeline, ticket to PR pipeline, tracker ticket pipeline.
semantic-release-convention-skill
Source of truth for commit-to-PR-to-merge-to-release conventions — semver labels, branch-aware tagging, changelogs, release pipelines.
version-bump-standard-skill
Consistent version bumping and release workflows — dev-to-uat-to-main flow, PR-label-driven semver. Use when setting up or auditing release workflows or onboarding a repo.
git-branch-workflow-setup-skill
Orchestrate dev-to-uat-to-main branch workflow setup during project init — detects need, prompts user via question tool, delegates to repo-ops-specialist-subagent.
git-semantic-commits-skill
Conventional Commits — type, scope, breaking changes, semver guidance, atomic-commit granularity by layer. Triggers: commit and push, make a commit, write a commit message, commit message format, semantic commit. Not for brevity (git-compact-commits-skill).