Borrowing it
Nothing to install: this file belongs to hristo2612/jinn. 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/hristo2612/jinn/main/.claude/skills/release-jinn-cli/SKILL.mdgit clone --depth 1 https://github.com/hristo2612/jinnWrote 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/hristo2612/jinn/release-jinn-cli)<a href="https://agentmods.dev/skills/hristo2612/jinn/release-jinn-cli"><img src="https://agentmods.dev/badge/skills/hristo2612/jinn/release-jinn-cli/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/hristo2612/jinn/release-jinn-cli"><img src="https://agentmods.dev/badge/skills/hristo2612/jinn/release-jinn-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
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 →
- high Privilege Escalation · line 62 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 71 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 70 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00058 | $0.01140 |
| Opus 5 | $0.00029 | $0.00570 |
| Sonnet 5 | $0.00012 | $0.00228 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
release-jinn-cli 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 9d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing jinn-cli
The published npm package is jinn-cli (lives in packages/jinn). The root
package (jinn) is private; packages/web is internal (its version isn't shipped).
Version lives in one place: packages/jinn/package.json.
How the pieces connect
- npm: published manually with
npm publishfrompackages/jinn. The package shipsdist/andtemplate/(see itsfiles), so you MUST build first. - GitHub release: created for tag
vX.Y.Z. - Homebrew:
.github/workflows/bump-formula.ymlfires onrelease: published. It waits (up to ~5 min) for the npm tarball atregistry.npmjs.org/jinn-cli/-/jinn-cli-X.Y.Z.tgz, computes its sha256, rewritesFormula/jinn.rb, and pushes the bump tomain. - CI (
ci.yml) runs typecheck/test/build onmain+ PRs. It does not publish.
Order matters: publish to npm before publishing the GitHub release, or the formula-bump job will wait and then fail because the tarball isn't on npm yet.
Steps
-
Land the work on
main(merge the PR). Releases are cut frommain; the formula-bump job also pushes tomain. Ensure a clean tree:git status. -
Pick the version. This is
0.x, so a minor bump (0.N.0) is fine even for small breaking changes; patch (0.x.N) for fixes only. -
Bump + commit (no
Co-Authored-By: Claudetrailer - repo convention):# edit packages/jinn/package.json "version" git commit -am "chore(release): jinn-cli vX.Y.Z" -
Generate and review the instance migration gate. Resolve the previous release tag, then run:
PREVIOUS_TAG="$(git describe --tags --abbrev=0 HEAD^)" VERSION="$(node -p "require('./packages/jinn/package.json').version")" pnpm --filter jinn-cli migration:generate -- --base-ref "$PREVIOUS_TAG" --version "$VERSION" pnpm --filter jinn-cli migration:check -- --base-ref "$PREVIOUS_TAG" --version "$VERSION"If there are no instance-template changes, record that fact; do not create an empty bundle. Otherwise review the preserved rationale and exact manifest paths. The generator owns the payloads and per-file merge instructions.
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.
- 9d ago First seen · 92 lines · 58 tokens per session scan A ee1484014966
release-jinn-cli is a skill published in the GitHub repository hristo2612/jinn (315 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 1,140 once invoked, about $0.0003 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-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.