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 skills add ccarvalho-eng/codex-elixir-phoenix --skill elixir-phoenix-hex-publishgit clone --depth 1 https://github.com/ccarvalho-eng/codex-elixir-phoenixWrote 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/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-hex-publish)<a href="https://agentmods.dev/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-hex-publish"><img src="https://agentmods.dev/badge/skills/ccarvalho-eng/codex-elixir-phoenix/elixir-phoenix-hex-publish.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.00029 | $0.00852 |
| Opus 5 | $0.00015 | $0.00426 |
| Sonnet 5 | $0.00006 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
elixir-phoenix-hex-publish 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hex Publish
This skill prepares and publishes Hex.pm releases for Elixir libraries with a repeatable release workflow. Use it when the user wants to cut a new version, check whether docs or wiki content need updates, create the release tag, publish to GitHub, or publish to Hex.
Workflow
- Build release context.
- Update release artifacts.
- Validate locally.
- Create the git tag and GitHub release.
- Publish to Hex.
Build Release Context
- Read
mix.exs,CHANGELOG.md, andREADME.mdfirst. - Inspect recent tags with
git tag --sort=-creatordate. - Inspect the current worktree with
git status --short. - Infer the next version only if the intended bump is obvious from the request or existing draft changes. Otherwise ask.
- Check whether the README is outdated relative to the release.
- Check whether the same changes should be reflected in the project wiki. If the repo uses a separate wiki and local wiki content is unavailable, call that out explicitly instead of guessing.
Update Release Artifacts
- Update
mix.exsversion. - Update
CHANGELOG.mdusing Keep a Changelog style and the release date inYYYY-MM-DD. ONLY list final diff with main. e.g. only add fixes if they were broken on main. - If README content is stale, update it in the same change set.
- If wiki updates are needed but the wiki is not locally available, mention the exact sections that should be updated in the final response.
- Keep release changes focused. Do not mix unrelated refactors into the release commit.
Validate Locally
- Use project-specific validation commands when present.
- For Phoenix projects, prefer the repo alias if one exists. For Aludel, run
mix precommitwhen release edits are complete. - If dependency state is out of sync, fix that first with the smallest necessary command such as
mix deps.get. - Do not tag or publish if validation is failing unless the user explicitly asks to bypass checks.
Create Release Artifacts
- Confirm the target version before creating release artifacts.
- Create an annotated tag using the repo convention. Prefer
vX.Y.Zif existing tags use that pattern. - Push the branch and tag only after local validation passes.
- Create the GitHub release with
gh release createwhen GitHub CLI is available and authenticated. - Use the changelog section for release notes when practical.
What ships with it
2 files 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 · 78 lines · 29 tokens per session scan A 2d7ee2bd5478
elixir-phoenix-hex-publish is a skill published in the GitHub repository ccarvalho-eng/codex-elixir-phoenix (11 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 852 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
release
Evaluate readiness and publish to crates.io.
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.
multi-repo-release
Prepares and validates GPT-RAG umbrella and multi-repository releases. Use whenever work involves release preparation, semantic versions, release branches, manifest or component pins, changelog release entries, tags, GitHub Release notes, or AI Landing Zone release alignment.
release-process
Pre-release validation, npm publish procedures, and post-publish verification.
crawlkit
Maintain and release the crawlkit Go library, preserving downstream compatibility for gitcrawl, slacrawl, discrawl, and notcrawl.
pi-sync
Daily upstream-sync job for the pi Go port — fetch upstream pi, triage every change since the recorded pin, port what's in scope, verify idiomatic + parity via independent reviews, update the ledger, and push. Use for "sync with upstream", "porting job", or as the scheduled daily run.