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/greenlv/skillferry/release-checklistnpx skills add GreenLv/skillferry --skill release-checklistgit clone --depth 1 https://github.com/GreenLv/skillferryWrote 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/greenlv/skillferry/release-checklist)<a href="https://agentmods.dev/skills/greenlv/skillferry/release-checklist"><img src="https://agentmods.dev/badge/skills/greenlv/skillferry/release-checklist.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.00033 | $0.00423 |
| Opus 5 | $0.00016 | $0.00211 |
| Sonnet 5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
release-checklist 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.
What it actually says
release-checklist
A compact, order-preserving release checklist for small-to-medium software
repositories. Demonstrates skillferry skill layout: targets frontmatter,
plus a references/ file the agent can open for details.
When to use
- Before tagging a version, publishing a package, or cutting a GitHub release.
- When asked "is this ready to release?" without a checklist at hand.
Checklist
- Tests: full unit + contract + negative tests pass locally on the release platform. Record the exact command and output tail as evidence.
- Public-tree audit: no secrets, credentials, machine paths, or runtime
state in the tree (
scripts/audit_public_tree.py .or equivalent). - Changelog: every user-visible change since the last tag is listed under the new version heading.
- Version: the version string is bumped in exactly one place of truth.
- Artifacts: built from a clean checkout; wheel/sdist (or equivalent) build and install in a fresh environment.
- Rollback: the previous release can be reinstalled; backups or revert steps are documented.
- Post-release verification: after publish, read back the published artifact/visibility/branch state before announcing success.
Rules
- Never infer whole-release success from one green signal; each gate must produce its own evidence.
- A failed gate is a blocker, not a note. Fix or downgrade the release scope.
- Record the checklist outcome (date, version, gates, evidence) in the repo.
See also
references/release-gates.mdfor per-gate details and acceptance evidence.
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 First seen · 45 lines · 33 tokens per session scan A 2f81134c9882
release-checklist is a skill published in the GitHub repository GreenLv/skillferry (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 33 tokens to every session and 423 once invoked, about $0.0002 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 skills, from other repositories
tutti-app-release
Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…
github
Git commits, pushes, and GitHub operations using tokenlean. Covers tl push (with multi-file safety guard), tl commit-prep, tl gh (bulk issue/PR/release operations), and when to use tl gh vs gh CLI vs GitHub MCP. Use when committing, pushing, creating/closing/viewing issues, managing PRs, creating releases, or any…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
r3f-animation
React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…