What is next-release?

A release runbook for publishing a new latexml-oxide version through its required build and distribution steps. It covers release candidates and final releases across several package and deployment channels.

Use it to prepare and publish a release to GitHub, container registries, Homebrew, crates.io, and ar5iv, following the project’s required checks.

It prevents version and tag mismatches, publishing prereleases as stable versions, skipping validation gates, or releasing targets in the wrong order.

How dginev/latexml-oxide configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to dginev/latexml-oxide. 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/dginev/latexml-oxide/main/.claude/skills/next-release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/dginev/latexml-oxide

Made for: Claude Code.

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/dginev/latexml-oxide/next-release/github.svg)](https://agentmods.dev/skills/dginev/latexml-oxide/next-release)

Your own site

<a href="https://agentmods.dev/skills/dginev/latexml-oxide/next-release"><img src="https://agentmods.dev/badge/skills/dginev/latexml-oxide/next-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/dginev/latexml-oxide/next-release"><img src="https://agentmods.dev/badge/skills/dginev/latexml-oxide/next-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found 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.00167	$0.02033
Opus 5.5	$0.00067	$0.00813
Sonnet 5.5	$0.00033	$0.00407
Haiku 4.5	$0.00017	$0.00203

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

Security

Grade A, and why

next-release scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -H "User-Agent: x" https://crates.io/api/v1/crates/<name> | grep -o '"max_version":"[^"]*"'

.claude/skills/next-release/SKILL.md · 126 lines

How it starts

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

Cutting a latexml-oxide release

docs/release/RELEASING.md is the authoritative procedure and CRATES_IO_PUBLISH.md the trap ledger — read them. This skill is the ordered, gated runbook distilled from the 0.7.5 cut, with the exact commands and the failure modes that bite.

Ground rules

The tag string must equal latexml_oxide/Cargo.toml's version. tools/make_release.sh hard-fails on GITHUB_REF_NAME != version. Tags are bare (0.7.5, no v prefix).
RC vs final is decided purely by a - in the tag. release.yml: a tag containing - (0.7.5-rc6) → draft prerelease, no containers/homebrew/crates. A bare tag (0.7.5) → public Release, auto-published, and fires the containers job.
Never publish an -rc to crates.io (cargo install ignores prereleases → users stay on the old stable). Final only.
All repo edits go via branch + PR (never commit to main). Release-prep and the promotion are each a PR.
Cargo.lock is gitignored here — don't try to commit it.

The two-gate rule for crates.io

crates.io is the LAST target and publishes only behind both gates on the FINAL tag:

Gate A — the public GitHub Release shows all platform binaries built/generated.
Gate B — the gh-pages docs build is healthy (Deploy Docs to GitHub Pages green on the release commit; crates.io's documentation link points at gh-pages).

Sequence

0. Pre-flight

Green main (cargo nextest run --workspace, N/0).
#512 toolchain pin: the fat-LTO maxperf release build OOMs on regressed nightlies. rust-toolchain.toml should pin a known-good dated nightly (e.g. nightly-2026-07-27); CI + release resolve through this file (proven by the 0.7.0 pin). Revert to floating channel = "nightly" once #512 closes. Confirm the pin is a good nightly before cutting.

1. Subcrate version bumps (for the crates.io republish) — the easy-to-miss step

crates.io is immutable: you cannot republish an existing version with new bytes. Every sibling crate that changed since the last publish needs a fresh version + matching dep pins, or cargo publish --workspace publishes only the top crate against stale siblings → downstream build breakage. Check each sibling's diff since the last release tag and bump honest 0.x semver (minor = API-affecting, patch = internal-only). Update every intra-workspace path+version pin (latexml_oxide + inter-crate). cargo set-version (cargo-edit) automates the cascade if installed; otherwise script it and verify with cargo metadata + cargo check --workspace.

Read the full file on GitHub · 126 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 · 126 lines · 167 tokens per session scan A 8b01ea035454

Subscribe to this mod's changes

next-release is a skill published in the GitHub repository dginev/latexml-oxide (18 stars, last pushed yesterday), licensed CC0-1.0. It adds 167 tokens to every session and 2,033 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow LaTeX Releases epub html jats math-parsing mathml

next-release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
next-releasedginev/latexml-oxide	Skill	18	yesterday	CC0-1.0	A	167	Claude Code
refactor-research-codeShaishavMaisuria/research-paper-lifecycle-skills	Skill	60	13d ago	Apache-2.0	A	60	Claude Code, Codex
infrastructure-publishingdocxology/template	Skill	23	today	Apache-2.0	A	127	Claude Code, Codex
template-publishdocxology/template	Skill	23	today	Apache-2.0	A	52	Claude Code, Codex
inclusio-publishersebastienrousseau/inclusio	Skill	0	2d ago	Apache-2.0	A	30	Claude Code, Codex
release-announcementpaperclipai/paperclip	Skill	111k	yesterday	MIT	A	42	Claude Code, Codex
releasethedotmack/claude-mem	Skill	114k	yesterday	Apache-2.0	A	13	Claude Code

latexml-oxide: Skill for Claude Code