Borrowing it
Nothing to install: this file belongs to zifeo/lade. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zifeo/lade/main/.cursor/skills/lade-release/SKILL.mdgit clone --depth 1 https://github.com/zifeo/ladeWrote 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/zifeo/lade/lade-release)<a href="https://agentmods.dev/skills/zifeo/lade/lade-release"><img src="https://agentmods.dev/badge/skills/zifeo/lade/lade-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/zifeo/lade/lade-release"><img src="https://agentmods.dev/badge/skills/zifeo/lade/lade-release.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.00050 | $0.00792 |
| Opus 5.5 | $0.00020 | $0.00317 |
| Sonnet 5.5 | $0.00010 | $0.00158 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
lade-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 1mo 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lade release
Scope
Release prep touches:
CHANGELOG.md(Keep a Changelog format)- Crate versions via
cargo set-version --workspace(lade,lade-sdk,age-plugin-lade, including path deps) - Crate versions only. There is no APM package.
Never commit, tag, or push — the user handles git.
Changelog workflow
-
Find the base tag
git tag --sort=-v:refname | head -5 git log <last-tag>..HEAD --format="%h %s" -
Read
[Unreleased]inCHANGELOG.md. Every user-facing item there should land in the new version section. -
Cross-check commits since the last tag. Add anything missing from
[Unreleased](group under Added / Changed / Fixed / Removed). Skip routinechore(deps)unless security-relevant. -
Promote
[Unreleased]→[X.Y.Z] - YYYY-MM-DD- Use today's date for stable releases.
- Leave an empty
## [Unreleased]section at the top. - Add a compare link immediately after the new section:
[X.Y.Z]: https://github.com/zifeo/lade/compare/v<prev>...vX.Y.Z - Previous tag is usually the last stable tag on
main(ignore unreleased beta tags unless the user says otherwise).
-
Writing style (match existing entries):
- Lead with bold feature name, then PR link
([#NNN](https://github.com/zifeo/lade/pull/NNN)). - One line per item; explain why when behavior changes.
- Categories: Added, Changed, Fixed, Removed (omit empty categories).
- Lead with bold feature name, then PR link
Version bump
Use scripts/set-version.sh, not a bare cargo set-version and not a hand edit of Cargo.toml:
bash scripts/set-version.sh X.Y.Z
cargo test --workspace --locked
The script runs cargo set-version --workspace (lade, lade-sdk, age-plugin-lade, path deps). Run tests (same as CI) to refresh Cargo.lock and verify the bump.
If cargo set-version is missing: cargo install cargo-edit. CI beta bumps use bash scripts/set-version.sh --bump beta.
GitHub release notes
The tag workflow publishes the matching CHANGELOG.md section with parse-changelog. Write that section before tagging. If the GitHub release already exists, its title and notes stay as first published. A crashed job is recovered by re-running that job. An asset already on the release is left in place.
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.
- 1mo ago Changed deb52a9ee118
- 1mo ago Changed 63f79b35b764
- 1mo ago Changed · -3 lines 36f7a1ca30f2
- 1mo ago Changed · +5 lines aae62d90ff29
- 2mo ago First seen · 72 lines · 50 tokens per session scan A 32d712989a99
lade-release is a skill published in the GitHub repository zifeo/lade (136 stars, last pushed today), licensed MPL-2.0. It adds 50 tokens to every session and 792 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
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.
release
Evaluate readiness and publish to crates.io.
cargo-release
PM-invocable protocol for Cargo publish and release operations in the trusty-tools Rust monorepo: semver rules, 10-step release sequence, macOS codesign safety, and cross-crate dependency ordering.
cargo-publish
Operate the socket-release crates.io flow - the cargo staged model (dry-run default), trusted publishing via OIDC under the cargo-publish environment, index-propagation waits, and yank-as-rollback. Use when publishing a Rust crate in a repo carrying scripts/socket-release/.
publish-rust
Verify and release a Rust crate or workspace. Bumps version, commits, tags, pushes. CI-driven by default; --local publishes directly.
jackin-release
Use only when the user explicitly requests this skill. Cuts a jackin❯ release — runs the readiness gates, writes the changelog, recommends a version, then executes cargo release on explicit operator confirmation.