A release procedure for Hex packages, which are reusable Elixir and Erlang libraries published to the Hex package registry. It supports automated releases through GitHub Actions and manual releases from a local project.

Use it to prepare a release, increase a package version, create a release tag, generate a changelog, or publish a package through an automated or manual workflow.

It adds checks before publishing, including package version, dependencies, repository changes, and branch state. This helps catch release blockers before a package is sent to Hex.

How agentjido/jido_ai configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to agentjido/jido_ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/agentjido/jido_ai/main/.agents/skills/hex-release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/agentjido/jido_ai

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/agentjido/jido_ai/hex-release/github.svg)](https://agentmods.dev/skills/agentjido/jido_ai/hex-release)

Your own site

<a href="https://agentmods.dev/skills/agentjido/jido_ai/hex-release"><img src="https://agentmods.dev/badge/skills/agentjido/jido_ai/hex-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/agentjido/jido_ai/hex-release"><img src="https://agentmods.dev/badge/skills/agentjido/jido_ai/hex-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,030 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00059	$0.02030
Opus 5.5	$0.00024	$0.00812
Sonnet 5.5	$0.00012	$0.00406
Haiku 4.5	$0.00006	$0.00203

Measured 2mo ago against content hash e4dd7b750b4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hex-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 2mo 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.

Origin

This is a copy

100% identical to hex-release — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/hex-release/SKILL.md · 301 lines

How it starts

The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Hex Release (Human-in-the-Loop)

Interactive workflow for releasing a Hex package with manual verification at each step. Supports two release paths: automated (via GitHub Actions) and manual (local).

When to Use

Use this skill when asked to:

Release a new version to Hex
Bump the package version
Prepare a release
Create a release tag
Trigger a release workflow

Pre-flight Checks

Before starting, run these checks automatically:

1. Identify the Package

Read mix.exs to determine:

Package name (from project() → :name or :app)
Current version (from @version or project() → :version)
Whether it has git_ops as a dependency (required for automated release)

2. Check for Git Dependencies

grep -E 'github:|git:|path:' mix.exs

Categorize any git/path deps found:

dev/test only (only: [:dev, :test]): Will not block Hex publish — note but continue
runtime deps: STOP — these block mix hex.publish. Tell the user which deps need to be published to Hex first or switched to Hex versions

3. Git Status

git status --porcelain

If dirty, STOP and ask user to commit or stash changes first.

4. Verify Branch

git branch --show-current

Confirm user is on main. Warn if on a different branch.

5. Check for Releasable Commits

git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo "")..HEAD

If no commits since last tag, STOP — nothing to release.

Review commits and confirm they follow conventional commit format (feat:, fix:, chore:, etc.). Non-conventional commits won't be picked up by git_ops for the CHANGELOG.

6. Run Tests

mix test

If tests fail, STOP and show failures.

7. Run Quality Checks

mix quality

This typically runs: format check, compile with warnings-as-errors, credo, and dialyzer. If the alias doesn't exist, run mix format --check-formatted && mix compile --warnings-as-errors as a minimum. If any check fails, STOP and show the issues.

Read the full file on GitHub · 301 lines

Changes

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.

2mo ago First seen · 301 lines · 59 tokens per session scan A e4dd7b750b4f

Subscribe to this mod's changes

hex-release is a skill published in the GitHub repository agentjido/jido_ai (211 stars, last pushed 2d ago), licensed Apache-2.0. It adds 59 tokens to every session and 2,030 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to hex-release, differing in 0 lines, and is treated as a copy.

Git and workflow LLM Releases ai ai-agents elixir elixir-package jido

github

GitHub via gh CLI: PRs, issues, reviews, repos, auth.

NousResearch/hermes-agent · 19 tokens

changelog

Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.

omnigent-ai/omnigent · 44 tokens

otto-drive-pr

PR mergeability, CI, and live preview.

omnigent-ai/omnigent · 14 tokens

github-repo-management

Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.

moltis-org/moltis · 47 tokens

goal-release

Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…

dyoshikawa/rulesync · 86 tokens

merge-pr

Merge a pull request using gh pr merge --admin.

dyoshikawa/rulesync · 13 tokens

jido_ai: Skill for Claude Code