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.02097 |
| Opus 5 | $0.00027 | $0.01048 |
| Sonnet 5 | $0.00011 | $0.00419 |
| Haiku 4.5 | $0.00005 | $0.00210 |
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 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 — 141 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.nexus.agentic (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
1 file 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.
- 3d ago Changed · -77 lines · +24 tokens per session ac0bb13de688
- 10d 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 (153 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 2,097 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-30.
Other skills, from other repositories
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
managing-app-versions
Manages semantic versioning for mobile apps across iOS and Android platforms. Use when the user says "bump version", "increment build number", "set version to", "release patch/minor/major", or "sync build numbers". Single source of truth is .msd/versions/{app-id}/version.json. Syncs to app.json (Expo), Info.plist…
submitting-app-release
Runs pre-flight validation gates and submits the app to App Store Connect and Google Play Console via EAS CLI. Use when the user says "release", "submit to store", "publish", "deploy app", or "submit for review". Always runs release-checklist.js first — never submits past a failing gate without explicit user…
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, canonical sync, Core preview checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release.
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
kappmaker-publish
Build, sign and ship a KAppMaker app — Fastlane setup, signed Android AAB, keystore generation, and uploading to Google Play and the App Store. Use when the user asks to build a release, create a keystore, configure fastlane, ship, upload or publish the app. Building iOS without a Mac is kappmaker-ios-ci.