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 agentmods add skills/thettwe/nyann/hotfixnpx skills add thettwe/nyann --skill hotfixgit clone --depth 1 https://github.com/thettwe/nyannWrote 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/thettwe/nyann/hotfix)<a href="https://agentmods.dev/skills/thettwe/nyann/hotfix"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/hotfix.svg" alt="Measured on agentmods" 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.00172 | $0.01031 |
| Opus 5 | $0.00086 | $0.00515 |
| Sonnet 5 | $0.00034 | $0.00206 |
| Haiku 4.5 | $0.00017 | $0.00103 |
Grade A, and why
hotfix 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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hotfix
Wraps bin/hotfix.sh. Creates the two branches a patch-release
flow needs:
release/<major>.<minor>— long-lived, branched from the source tag. Idempotent: reused if it already exists. Future patches on the same minor go on the same branch.hotfix/<slug>— short-lived, branched off the release branch. The user commits the actual fix here.
After this skill: the user makes the fix, commits, then runs
/nyann:release from the hotfix branch.
1. Resolve the source tag
Before invoking, confirm the source tag with the user:
- "I want to patch v1.2.0" →
--from v1.2.0. - "I want to fix something in the previous minor" → ask which tag exactly.
- If they said "patch the latest release" without naming a tag,
list
git tag --sort=-v:refname | head -5and ask.
2. Pick a slug
Ask: "what's the change?" Convert their answer to a slug:
- "Fix the broken auth callback" →
fix-auth-callback - "Patch the SQLi in the user-search endpoint" →
patch-sqli-user-search
The script enforces lowercase + alphanumeric + hyphen; it'll reject anything else.
3. Invoke
bin/hotfix.sh --target <cwd> --from <tag> --slug <slug> --checkout
--checkout switches to the hotfix branch immediately. Skip it
when the user has uncommitted work in the current branch (the
script will warn about a dirty tree if checkout fails — don't
let it half-finish).
4. Hand back the next-steps
The output JSON includes a next_steps[] array with the exact
commands to run next:
- (skip if --checkout was used)
git checkout hotfix/<slug> - Make the fix, commit it (use
/nyann:commitfor a Conventional Commits message). - Merge the hotfix into the release branch:
git checkout release/<m>.<n> && git merge --no-ff hotfix/<slug>. - Run
/nyann:release --version <patch> --pushfrom the release branch. The script suggests the patch version (source-tag + 1 in the patch slot) — confirm with the user before passing it through.release.shoperates on the current branch (HEAD), so the merge step in (3) is what puts the right commits on the lineage that gets tagged.
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.
- 2d ago First seen · 99 lines · 172 tokens per session scan A 3b27d29f5269
hotfix is a skill published in the GitHub repository thettwe/nyann (6 stars, last pushed 7d ago), licensed MIT. It adds 172 tokens to every session and 1,031 once invoked, about $0.0009 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
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
create-release-checklist
Create a release checklist and GitHub issue for an R package. Use when the user asks to "create a release checklist" or "start a release" for an R package.
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
craft-plugin-release
Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist…
publish-github-release
Use this whenever the user asks to ship, publish, release, tag, or cut a new version of the project — OR when CHANGELOG.md has an "Unreleased" / in-progress section ready to be shipped. The skill bumps the version across all version-bearing files, regenerates the CHANGELOG entry from git log since the last tag…
wp-org-submission
Use when submitting a WordPress plugin to the WP.org directory for the first time, deploying a new version via SVN (plugins.svn.wordpress.org trunk, tags, assets), fixing a reviewer rejection (17-issue catalog with exact reviewer quotes), writing or correcting readme.txt (Stable tag, Changelog, Upgrade Notice…