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/agentjido/jido_ai/hex-releasenpx skills add agentjido/jido_ai --skill hex-releasegit clone --depth 1 https://github.com/agentjido/jido_aiWrote 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/agentjido/jido_ai/hex-release)<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="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.00059 | $0.02030 |
| Opus 5 | $0.00030 | $0.01015 |
| Sonnet 5 | $0.00012 | $0.00406 |
| Haiku 4.5 | $0.00006 | $0.00203 |
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 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.
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.
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()→:nameor:app) - Current version (from
@versionorproject()→:version) - Whether it has
git_opsas 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.
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 · 301 lines · 59 tokens per session scan A e4dd7b750b4f
hex-release is a skill published in the GitHub repository agentjido/jido_ai (203 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 2,030 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
release
Prepare and publish stable Agent Lightning releases through the repository's version bump, pull-request checks, merge, tag, PyPI trusted-publishing, and versioned-documentation workflows. Use when asked to plan, cut, verify, or explain a release; treat nightly TestPyPI builds as a separate path.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…
release-checklist
Pre-release safety audit for the Bifrost repo. Scans database migrations changed in a release for high-scale deadlock / lock-contention risks and for work that blocks application boot time, then produces a pass/warn/fail report with a concrete remediation plan. Invoked with /release-checklist [git-ref-range]. Built to…
release-validation
Use this skill when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally built release bundles on user-approved real hosts and private meshes, deciding release readiness, or producing a formal…
release
Cut an AgentOS release via the scripts/publish flow. Use when the user asks to release, publish, cut a release, or bump the AgentOS version.