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 commands/thettwe/nyann/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/commands/thettwe/nyann/hotfix)<a href="https://agentmods.dev/commands/thettwe/nyann/hotfix"><img src="https://agentmods.dev/badge/commands/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 | $0.00069 | $0.00836 |
| Opus 5 | $0.00034 | $0.00418 |
| Sonnet 5 | $0.00014 | $0.00167 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
nyann: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 3d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin root: This is a Claude Code plugin, NOT a CLI tool. Do NOT
search via which, npm list, pip list, or brew list. This file
is at <plugin_root>/commands/. All scripts: <plugin_root>/bin/.
Read the matching skills/*/SKILL.md for the full flow.
/nyann:hotfix
Wraps bin/hotfix.sh. Minimal-state setup: this command creates
branches, the user commits the fix, then /nyann:release does the
tag + push.
Safety
- Refuses to overwrite an existing
hotfix/<slug>branch (no silent stomp of in-progress work). - Reuses an existing
release/<major>.<minor>branch idempotently (multiple patches on the same minor live on the same branch). - Source tag must exist locally — explicit error if missing, with a
hint to
git fetch --tags origin.
Output
A HotfixResult JSON. Most useful field is next_steps[] — concrete
commands the user runs to take the hotfix from setup to shipped:
- (Optional)
git checkout hotfix/<slug>— only when --checkout wasn't passed. - Make the fix, commit it.
git checkout release/<m>.<n> && git merge --no-ff hotfix/<slug>/nyann:release --version <suggested-patch> --push(from the release branch — release.sh tags HEAD).
When to invoke
- "I need to patch v1.2.0" → run this.
- "Backport this fix to the previous minor" → run this against the most recent tag on that minor.
- "We have a security issue in the v1 line" → run this; release.sh's
prerelease detection handles
-rcsuffixes if you want a pre-release patch.
When NOT to invoke
- The user just wants a feature branch (no release-branch lineage):
/nyann:branch fix <slug>. - The user already has the hotfix branch ready and committed: merge
into the release branch first (
git checkout <release> && git merge --no-ff <hotfix>), then/nyann:release --version <patch>.
See also:
/nyann:release— the tag + push step that runs after this./nyann:branch— for non-hotfix branches (no tag lineage)./nyann:cleanup-branches— prunehotfix/<slug>after the release has merged back to main.
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.
- 3d ago First seen · 77 lines · 69 tokens per session scan A 7086b487dc8d
nyann:hotfix is a command published in the GitHub repository thettwe/nyann (6 stars, last pushed 4d ago), licensed MIT. It adds 69 tokens to every session and 836 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-08-31.
Other commands, from other repositories
create-namespace
Slash command that creates a new namespace file under system/namespaces/ in the personal repo, with lifecyclestate: scratch.
generate-release-notes
Generate comprehensive release notes from merged PRs between releases.
release
Prepare a release: bump version, finalize CHANGELOG, and show the git tag command.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.