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-release-checknpx skills add jackin-project/jackin-dev --skill jackin-release-checkgit 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-check)<a href="https://agentmods.dev/skills/jackin-project/jackin-dev/jackin-release-check"><img src="https://agentmods.dev/badge/skills/jackin-project/jackin-dev/jackin-release-check.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.1 | $0.00026 | $0.00833 |
| Opus 5 | $0.00013 | $0.00417 |
| Sonnet 5 | $0.00005 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
jackin-release-check 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 6d 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-check
Run the release-readiness gates. Each gate is binary — green passes, red blocks — and the release is ready only when every gate is green (warnings surface but do not block). The commands are the repo's own (from CONTRIBUTING.md merge-readiness + .github/workflows/ci.yml), never stripped-down substitutes.
When to use
- Before cutting a release, or when the operator asks whether the project is release-ready.
When NOT to use
- Cutting the release itself →
jackin-release(it runs this skill as its first gate).
Process
Run each gate in order; collect a green / red / skip verdict into a one-line-per-gate report.
-
CI gate.
gh run list --workflow=ci.yml --branch=main --limit=1 --json conclusion --jq '.[0].conclusion'— green only onsuccess. Ifdocker/construct/**ordocs/**changed since the last tag (git diff --name-only <last-tag>..HEAD -- <path>), also requireconstruct.yml/docs.ymlgreen on main.Done when every CI workflow that owns a changed path is green.
-
Static gates.
cargo fmt --check;cargo clippy --all-targets --all-features -- -D warnings. Red on any violation.Done when both exit 0.
-
Test gate.
cargo nextest run --all-features;cargo nextest run -p jackin --features e2e --profile docker-e2e. Red on any failure.Done when both suites pass.
-
Doc-link gate. Walk internal links under
docs/content/docs/(relative paths +hrefs); verify each target file exists. Red only on a broken link to a shipped page; warn on external URLs you cannot reach.Done when every internal link resolves.
-
TODO freshness. Read
TODO.mdandtodo/; flag items referencing completed work or showing no recent activity. Warn — does not block.Done when every TODO item is either live or flagged stale.
-
Security exceptions. Read
SECURITY_EXCEPTIONS.md; ask the operator whether each entry is still current. Review (blocks) until confirmed or the file is updated and re-read.
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.
- 6d ago First seen · 64 lines · 26 tokens per session scan A c6b9fda70e51
jackin-release-check is a skill published in the GitHub repository jackin-project/jackin-dev (3 stars, last pushed 5d ago), licensed Apache-2.0. It adds 26 tokens to every session and 833 once invoked, about $0.0001 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
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
verify-and-ship
Run all quality checks (tests, lint, typecheck), fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
ship-workflow
Automated release pipeline: merges main, runs tests, pre-landing review, version bump, changelog, bisectable commits, and PR creation. Triggers on: "ship it", "release this", "prepare for release", "open a PR", "push and PR", "land this", "/ship-workflow".
AI Release Guardian
Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.
repo-harness-check
Verification entrypoint for repo-harness workflow readiness. Runs workflow gates, task sync, contract checks, inspector, and migration dry-run before merge or release.
mathodology-dev-test-release
Use when validating the Mathodology skills-only repository or preserving archived knowledge about the former development, testing, deployment, packaging, and release workflows.