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 luochang212/skill-zoo --skill app-releasegit clone --depth 1 https://github.com/luochang212/skill-zooWrote 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/luochang212/skill-zoo/app-release)<a href="https://agentmods.dev/skills/luochang212/skill-zoo/app-release"><img src="https://agentmods.dev/badge/skills/luochang212/skill-zoo/app-release/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/luochang212/skill-zoo/app-release"><img src="https://agentmods.dev/badge/skills/luochang212/skill-zoo/app-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 128 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00043 | $0.02537 |
| Opus 5.5 | $0.00017 | $0.01015 |
| Sonnet 5.5 | $0.00009 | $0.00507 |
| Haiku 4.5 | $0.00004 | $0.00254 |
Grade A, and why
app-release 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 today.
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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Overview
Release is done by pushing a v* tag. CI validates the release metadata, builds all platforms, creates a GitHub Release, and then updates the website version and Homebrew cask. Manual steps: update the changelog and version files, commit them together, then tag and push. The workflow is asynchronous: after a successful tag push, report that the release was triggered; do not wait for CI unless the user explicitly asks.
Announce at start: "I'm using the release skill to ship a new version."
When to Use
digraph when_release {
"User asks to release/ship/publish?" [shape=diamond];
"Use this skill" [shape=box];
"Homebrew 404 or artifact-not-found after a tag push?" [shape=diamond];
"Use this skill" [shape=box];
"Pre-release checks (code review, QA)?" [shape=diamond];
"Not this skill. Use requesting-code-review" [shape=box];
"User asks to release/ship/publish?" -> "Use this skill" [label="yes"];
"User asks to release/ship/publish?" -> "Homebrew 404 or artifact-not-found after a tag push?" [label="no"];
"Homebrew 404 or artifact-not-found after a tag push?" -> "Use this skill" [label="yes"];
"Homebrew 404 or artifact-not-found after a tag push?" -> "Pre-release checks (code review, QA)?" [label="no"];
"Pre-release checks (code review, QA)?" -> "Not this skill. Use requesting-code-review" [label="yes"];
}
Use when:
- User says "release", "ship", "publish", "new version", "bump version"
- Homebrew cask update failed (404 on DMG URLs)
- CI
create-releasejob failed to find artifacts
Don't use for:
- Code review before releasing
- Deciding WHAT version number (ask the user)
- Feature work or bug fixes
Quick Reference
| Step | Command |
|---|---|
| Check existing tags | git tag --sort=-v:refname | head -5 |
| Prerequisites (in order) | fmt → lint:rs → test → typecheck → lint → format:check → status |
| Check Rust formatting | cargo fmt --check --manifest-path src-tauri/Cargo.toml |
| Check Rust lint | bun run lint:rs |
| Check TypeScript types | bun run typecheck |
| Check frontend lint | bun run lint |
| Check frontend formatting | bun run format:check |
| Check independent website | npm --prefix site run check && npm --prefix site run build (browser checks below) |
| Check uncommitted changes | git status --short |
| Tag and push | git push origin main && git tag v<VERSION> && git push origin v<VERSION> |
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.
- today Changed 42722f0d72ce
- 2d ago Changed · +26 lines 1163ec84ca3d
- 1mo ago First seen · 161 lines · 43 tokens per session scan A 11d75fbf2b9e
app-release is a skill published in the GitHub repository luochang212/skill-zoo (123 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 2,537 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
skillshare-app-release
A release workflow for shipping the skillshare desktop application on macOS, Windows, and Linux. It coordinates the release pull request, automated builds, GitHub release, updater feed, and Homebrew package.
deployment-rules
Release/deployment standards — semantic-release, commitlint, version sync, the updater. Load for /prepare-release and changes to release.config.mjs / commitlint / workflows / version files. Owned by project-steward.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
release-testing-workflow
Use this skill when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA.
contribute-catalog
Author a new HyperFrames registry block (caption style, VFX block, transition, lower third) or component (text effect, overlay, snippet) and ship it as an upstream PR to the hyperframes repo. Use ONLY when the user wants to CONTRIBUTE to the public catalog — for in-project caption/transition authoring use the…
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.