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/hex-releasenpx skills add agentjido/jido --skill hex-releasegit clone --depth 1 https://github.com/agentjido/jidoWrote 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/hex-release)<a href="https://agentmods.dev/skills/agentjido/jido/hex-release"><img src="https://agentmods.dev/badge/skills/agentjido/jido/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 | $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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- hex-release — 100% identical, 0 lines differ
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.
- 4d ago First seen · 301 lines · 59 tokens per session scan A e4dd7b750b4f
hex-release is a skill published in the GitHub repository agentjido/jido (1,829 stars, last pushed 2d ago), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
deep-researcher
Performs comprehensive, multi-layered research on any topic with structured analysis and synthesis of information from multiple sources.
llmtornado-tutorial-generator
Generates comprehensive code tutorials on LlmTornado API formatted for Medium publication with examples, explanations, and best practices.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.