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 jig-hotfix-flowgit 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/jig-hotfix-flow)<a href="https://agentmods.dev/skills/0x0w1/jig/jig-hotfix-flow"><img src="https://agentmods.dev/badge/skills/0x0w1/jig/jig-hotfix-flow/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/jig-hotfix-flow"><img src="https://agentmods.dev/badge/skills/0x0w1/jig/jig-hotfix-flow.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.02352 |
| Opus 5 | $0.00032 | $0.01176 |
| Sonnet 5 | $0.00013 | $0.00470 |
| Haiku 4.5 | $0.00006 | $0.00235 |
Grade A, and why
jig-hotfix-flow 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- hotfix-flow — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hotfix Flow
Use this repository skill only when a defect already released on main must be fixed before the work waiting on develop is ready to ship.
Every other fix is an ordinary task. Use develop-task-flow and let the fix ride the next release.
When This Applies
All three must hold. If any one fails, this is not a hotfix.
- The defect is reachable from
main, so people already have it. - Harm keeps accumulating for as long as the released state stands. See Hotfix Triggers — the user calling it urgent is not that.
developholds work that must not ship yet. Whendevelophas nothing unreleased, there is no hotfix: fix it withdevelop-task-flowand release normally.
Hotfix Triggers
Whether a defect deserves to bypass the develop queue is a judgement, and it is made while something is on fire. So the judgement is not made here: the project writes the conditions in advance and this run only matches against them.
Resolve the list from the ## Hotfix Triggers section of the rubric file, found in the same order the grade uses:
JIG_VERSION_RUBRICenvironment variable.git config --local --get jig.versionRubric(repository override)..jig/versioning.md(the convention).
Accept either spelling of the section title: ## Hotfix Triggers or ## 핫픽스 트리거.
The section holds an anchoring question on a > line and the conditions answering it that the project has already recognised. When the rubric has no such section, use this default and say in the report that it was the default:
Does harm keep occurring and accumulating for as long as the released state stands?
- The released artifact does not install or start
- Data is lost or corrupted
- A credential or secret is exposed
- A published security vulnerability is exploitable
- A released capability is entirely broken for most users
Apply it in this order:
- A listed condition matches. Name it, record it as a
Hotfix-Trigger:trailer next toRelease-Grade:, and continue. - Nothing matches. Put the anchoring question to the user, in terms of what keeps happening while the release stands. A
noends the run: hand the fix todevelop-task-flowand say why. - Nothing matches but the answer is
yes. The list is short by one condition. Propose that condition, add it to the## Hotfix Triggerssection, and commit that change on its own before the hotfix starts. Then continue from step 1 with the condition now listed.
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.
- 6d ago First seen · 150 lines · 63 tokens per session scan A 173fb53227ab
jig-hotfix-flow is a skill published in the GitHub repository 0x0w1/jig (5 stars, last pushed 6d ago), licensed MIT. It adds 63 tokens to every session and 2,352 once invoked, about $0.0003 per session on Opus 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-09-03.
Other skills, from other repositories
github-release-briefing-skill
Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
release
Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…