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-releasegit 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-release)<a href="https://agentmods.dev/skills/0x0w1/jig/github-release"><img src="https://agentmods.dev/badge/skills/0x0w1/jig/github-release/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-release"><img src="https://agentmods.dev/badge/skills/0x0w1/jig/github-release.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.00068 | $0.03375 |
| Opus 5.5 | $0.00027 | $0.01350 |
| Sonnet 5.5 | $0.00014 | $0.00675 |
| Haiku 4.5 | $0.00007 | $0.00337 |
Grade A, and why
github-release 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 19d 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
97% identical to jig-github-release — 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Release
Use this repository skill for release execution.
Release Model
- A release promotes the current
origin/developtomainwith a fast-forward push:git push origin develop:main. There is no release PR and norelease/*branch. developmust already contain every intended release change, squash-merged throughdevelop-task-flow.- The bump is graded against this project's version rubric, not against a rule inside this skill. See Version Rubric.
- The next version is computed from the latest
vX.Y.Ztag using the graded bump type. See Version Format. - The release tag and GitHub release are created from the CLI with
git tagandgh release create. - Release notes are written by the agent from the commits in
<previous tag>..<new tag>, categorized by conventional commit prefix.
GitHub Profile
Before any gh command, resolve the host from JIG_GITHUB_HOST, local jig.githubHost, then github.com, and resolve the profile from JIG_GITHUB_PROFILE, then local jig.githubProfile. If a profile is configured, read its credential with gh auth token --hostname <host> --user <profile> without printing it and run every gh command with that credential through GH_TOKEN (github.com or *.ghe.com) or GH_ENTERPRISE_TOKEN (other hosts). Verify gh api user --jq .login matches the profile. Do not use gh auth switch; fall back to the globally active account only when neither the environment nor local config selects a profile.
Version Rubric
The grading rubric is not in this skill. It is a project-owned file, so every project grades by its own axis. The version-rubric skill owns that file.
Resolve the rubric path in this order:
JIG_VERSION_RUBRICenvironment variable (session-only override).git config --local --get jig.versionRubric(repository override)..jig/versioning.md(the convention).
Apply it like this:
- Grade with the rubric's
## Decision Order: ask its questions in order and stop at the first match. That ordering is fixed; a rubric cannot change it. - Check the graded bump against the rubric's
## Grade Definitionsbefore computing the version, and quote the deciding question in the report. - Apply
## Hard Rulesafter the ordered questions. A rubric without that section has no escalation rule. - A missing optional section (
## Hard Rules,## Interface Paths,## Release Notes,## Version Format,## Pre-Release Checks) means that rule does not apply. - Rubrics written before the contract switched to English carry Korean titles, and they stay valid. Accept either spelling for every section:
## 판정 순서,## 등급 정의,## 강경 규칙,## 인터페이스 경로,## 릴리즈 노트,## 버전 형식,## 릴리즈 전 검증, and> 기준:for> Basis:. Read the file as it is; never retitle it during a release. - Read sections beyond the contract as grading context; a project may list what counts as its public interface there.
- Report the rubric path, its source, and whether it records the adopted default or a project-specific rubric.
- Never edit the rubric file from this skill.
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.
- 19d ago Changed 22d9f8edd60f
- 1mo ago Changed 8857beddd436
- 1mo ago First seen · 187 lines · 68 tokens per session scan A 263816941720
github-release is a skill published in the GitHub repository 0x0w1/jig (5 stars, last pushed 20d ago), licensed MIT. It adds 68 tokens to every session and 3,375 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to jig-github-release, 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.
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.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.