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/jackin-project/jackin-dev/jackin-releasenpx skills add jackin-project/jackin-dev --skill jackin-releasegit clone --depth 1 https://github.com/jackin-project/jackin-devWrote 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/jackin-project/jackin-dev/jackin-release)<a href="https://agentmods.dev/skills/jackin-project/jackin-dev/jackin-release"><img src="https://agentmods.dev/badge/skills/jackin-project/jackin-dev/jackin-release.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.00045 | $0.00860 |
| Opus 5 | $0.00023 | $0.00430 |
| Sonnet 5 | $0.00009 | $0.00172 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
jackin-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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jackin-release
Cut a release. The only irreversible skill in the suite — cargo release --execute bumps the version, rewrites the changelog header, tags, and pushes. Hard-gated on one explicit operator "yes"; nothing releases on assumption.
Orchestrates jackin-release-check (the gates) and jackin-release-notes (the changelog), then recommends a version from the changelog shape and cuts.
When to use
- The operator asks to cut / ship / release a version.
When NOT to use
- Just checking readiness →
jackin-release-check. - Just updating the changelog →
jackin-release-notes.
Prerequisites
cargo-release installed; gh authenticated; release.toml with pre-release-replacements for CHANGELOG.md; CHANGELOG.md with the <!-- next-header --> marker; .github/workflows/ci.yml.
Process
-
Gates. Run
jackin-release-check. A red gate stops — show the report and name what to fix. Warns surface; ask whether to continue.Done when every gate is green, or the operator accepted the warns.
-
Changelog. Run
jackin-release-notes. Present the[Unreleased]section; let the operator re-classify or reword.Done when the operator approves the changelog.
-
Recommend a version. Read the approved
[Unreleased]buckets: any Removed or "breaking" entry → major; any Added → minor; only Fixed / Changed / Security / Deprecated → patch. Read the current version (grep '^version' Cargo.toml), compute the next, present the recommendation, wait.Done when the operator confirms the bump level.
-
Commit the changelog. If
CHANGELOG.mdhas uncommitted edits,git add CHANGELOG.md && git commit -m "docs: update changelog for vX.Y.Z". -
Final confirm. Show the summary — version, bump level, changelog shape, and the exact
cargo release <level> --executeabout to run (it bumpsCargo.toml, renames[Unreleased]to[X.Y.Z] - <date>viarelease.toml, tags, and pushes). Do not run it without an explicit "yes."
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.
- 4d ago First seen · 64 lines · 45 tokens per session scan A 2573a491fa53
jackin-release is a skill published in the GitHub repository jackin-project/jackin-dev (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 45 tokens to every session and 860 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-30.
Other skills, from other repositories
release
Evaluate readiness and publish to crates.io.
release-mcp
Release a new version of the tapo-mcp crate (MCP server), versioned independently from the tapo libraries.
release-process
End-to-end release runbook for playwright-rust — version bump, supply-chain refresh, per-crate CHANGELOGs, tag-prefix routing for the three workspace crates, the safer push-then-tag workflow that waits for CI before publishing, and the post-release follow-ups.
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.
rust-release
Plan and execute Rust release engineering. Use when: publishing a crate, setting up release automation, cross-compiling binaries. Do not use: for version bumping alone, local build setup.
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/.