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 version-rubricgit 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/version-rubric)<a href="https://agentmods.dev/skills/0x0w1/jig/version-rubric"><img src="https://agentmods.dev/badge/skills/0x0w1/jig/version-rubric/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/version-rubric"><img src="https://agentmods.dev/badge/skills/0x0w1/jig/version-rubric.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.00064 | $0.04414 |
| Opus 5.5 | $0.00026 | $0.01766 |
| Sonnet 5.5 | $0.00013 | $0.00883 |
| Haiku 4.5 | $0.00006 | $0.00441 |
Grade A, and why
version-rubric 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 29d 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
95% identical to jig-version-rubric — 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Rubric
Use this repository skill to decide and maintain how this project grades patch, minor, and major. The decision lives in a project-owned Markdown file that github-release reads at release time.
Run this skill whenever the rubric needs to be created, reviewed, or changed. It is safe to run repeatedly.
Rubric File
Resolve the rubric path in this order:
JIG_VERSION_RUBRICenvironment variable (session-only override).git config --local --get jig.versionRubric(repository override; not propagated by clone)..jig/versioning.md(the convention).
.jig/is owned by the project, not by jig. The installer andjig-updatenever write or delete it, andjig-doctornever treats it as drift.- The file must be committed.
git config --locallives in.git/configand is not propagated by clone or CI checkout, so a config-only setup grades differently for different people. - Never store state such as "the default was adopted" in a config key. That belongs in the file's
> Basis:line, which is the single record of the decision.
File Contract
Two required sections, six optional. The section titles are the contract.
# Version Policy
> Basis: jig default (human-intervention axis) | project-specific, <date>
## Decision Order (required)
1. <question> → `patch`
2. <question> → `minor`
3. <question> → `major`
## Grade Definitions (required)
| bump | definition |
## Hard Rules (optional) conditions that always escalate
## Interface Paths (optional) changed paths that set a starting grade
## Hotfix Triggers (optional) what justifies bypassing the develop queue
## Release Notes (optional) note section order and titles
## Version Format (optional) tag pattern, pre-1.0 handling, summary language
## Pre-Release Checks (optional) commands to run before releasing
## Decision Orderis asked in order and stops at the first match. A rubric cannot change that meaning.- An optional section a rubric omits simply does not apply to that project. No
## Hard Rulesmeans no escalation rule, even though the default below ships two. - The
> Basis:line records whether the default was adopted or the rubric was written for the project. - Sections beyond these are read as context, not ignored. A project may add its own, such as a list of what counts as its public interface.
What ships with it
20 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.
- rubrics/_template.md 3.5 KB
- rubrics/agent-skill-pack.md 3.2 KB
- rubrics/api-server.md 2.8 KB
- rubrics/background-worker.md 2.6 KB
- rubrics/cli-tool.md 2.5 KB
- rubrics/common.md 4.6 KB
- rubrics/config-collection.md 2.6 KB
- rubrics/content-site.md 2.8 KB
- rubrics/course-material.md 2.8 KB
- rubrics/data-pipeline.md 2.9 KB
- rubrics/dataset.md 2.8 KB
- rubrics/design-assets.md 2.6 KB
- rubrics/desktop-app.md 2.8 KB
- rubrics/document-archive.md 3.0 KB
- rubrics/INDEX.md 10 KB
- rubrics/infrastructure.md 2.9 KB
- rubrics/library-sdk.md 2.6 KB
- rubrics/mobile-app.md 2.8 KB
- rubrics/monorepo.md 3.7 KB
- rubrics/web-client.md 2.9 KB
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.
- 29d ago Changed · +12 lines 4c3f5a2f9c0c
- 1mo ago Changed · +1 lines 67267511e753
- 1mo ago Changed · +27 lines 4f00709f9414
- 2mo ago First seen · 210 lines · 64 tokens per session scan A f63537998963
version-rubric is a skill published in the GitHub repository 0x0w1/jig (5 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 4,414 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to jig-version-rubric, 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-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.
release
Fully automate a release with version-bump and childhood.