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 niki914/zafiro --skill release-new-versiongit clone --depth 1 https://github.com/niki914/zafiroWrote 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/niki914/zafiro/release-new-version)<a href="https://agentmods.dev/skills/niki914/zafiro/release-new-version"><img src="https://agentmods.dev/badge/skills/niki914/zafiro/release-new-version/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/niki914/zafiro/release-new-version"><img src="https://agentmods.dev/badge/skills/niki914/zafiro/release-new-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.02194 |
| Opus 5.5 | $0.00022 | $0.00878 |
| Sonnet 5.5 | $0.00011 | $0.00439 |
| Haiku 4.5 | $0.00005 | $0.00219 |
Grade A, and why
release-new-version 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 8d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release New Version
Release workflow for Zafiro.
Repos involved:
| Repo | Tag format | Release notes |
|---|---|---|
niki914/zafiro (main, open source) |
v<code>-<name> e.g. v8-1.1.0 |
Full bilingual notes |
Xposed-Modules-Repo/com.niki914.zafiro (closed) |
<code>-<name> e.g. 8-1.1.0 |
Same feature entries, closing line points back to the main repo. Optional — ask the user every time. |
One APK, two notes. CI builds and signs the APK and creates the Release when a tag is pushed to the main repo. There is no CI in the Xposed repo — its release is a manual gh operation. Never build locally.
Phase 1 — Gather facts
Collect all of this before asking the user anything:
- Local version: read
versionCode/versionNamefromapp/build.gradle.kts. - Latest release baseline:
gh release view -R niki914/zafiro(returns the latest non-draft, non-prerelease release by default). Parse its tagv<code>-<name>. - Version string locations: find every place the current version literal lives:
Only scan these extensions:rg -n '<current versionName>' -g '*.{md,kt,kts,txt,py}' .md,kt,kts,txt,py. Nothing else. rg respects.gitignoreby default — do not disable that. - Changes since last release: commits and merged PRs from the last release tag to
origin/main:git log v<code>-<name>..origin/main --oneline --no-merges gh pr list -R niki914/zafiro --state merged --limit 50 --json number,title --jq '.[] | "\(.number) \(.title)"' - If local
versionCode/versionNamedo not match the latest release tag: stop and ask the user how to proceed. Do not guess.
Summarize the changes for the user in plain language before drafting.
Phase 2 — Draft release notes (iterate until explicit approval)
Write bilingual notes (Chinese first, ---, then English) from the change list. Apply these rules strictly — they are derived from every historical release:
What ships with it
2 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.
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.
- 8d ago Changed · +12 lines bd22e1a6597a
- 17d ago Changed · +2 lines 4af7d7d95456
- 1mo ago Changed · -77 lines · +24 tokens per session ac0bb13de688
- 1mo ago First seen · 218 lines · 30 tokens per session scan A 1bd240a8b0f5
release-new-version is a skill published in the GitHub repository niki914/zafiro (300 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 2,194 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
release-kotlin-library
Use when preparing, publishing, or checking readiness for a Kotlin library release, including verifying its gradle-maven-publish-plugin prerequisite, reconciling changelogs and API snapshots, and checking publication.
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
ship-feature
Ship a feature end-to-end — update tests, docs, docs-site, then release to PyPI. Use when user says "ship", "ship feature", "release", or asks to publish a new version.