renux: Skill for Claude Code

.agents/skills/release/SKILL.md

release is a skill for Claude Code, Codex from andrianllmm/renux. It costs 45 tokens per session (403 once invoked), scanned A, original, MIT.

A release checklist for the renux Python project. It uses commitizen, a tool that reads structured commit messages to choose the next version, update the changelog, create a Git tag, and build the package.

In plain words
What is it for?
Use it to check the repository, calculate and apply a patch, minor, or major version bump, create the release commit and tag, and build distribution files.
Why use it?
It prevents version numbers from being changed inconsistently or releases being made from failing or uncommitted code. It also requires a preview before creating the release.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is andrianllmm/renux's own configuration. It tells Claude Code and Codex how to work on renux itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything renux configures →

Reuse

Borrowing it

Nothing to install: this file belongs to andrianllmm/renux. 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/andrianllmm/renux/main/.agents/skills/release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/andrianllmm/renux

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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/andrianllmm/renux/release/github.svg)](https://agentmods.dev/skills/andrianllmm/renux/release)
Your own site
<a href="https://agentmods.dev/skills/andrianllmm/renux/release"><img src="https://agentmods.dev/badge/skills/andrianllmm/renux/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/skills/andrianllmm/renux/release"><img src="https://agentmods.dev/badge/skills/andrianllmm/renux/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 403 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. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00403
Opus 5.5 $0.00018 $0.00161
Sonnet 5.5 $0.00009 $0.00081
Haiku 4.5 $0.00005 $0.00040

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

Security

Grade A, and why

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.

.agents/skills/release/SKILL.md · 49 lines

What it actually says

release

renux's version is derived from git tags via commitizen (version_provider = "pep621", tag_format = "v$version" in pyproject.toml). Never hand-edit the version in pyproject.toml or src/renux/__init__.py. Always go through cz bump.

Steps

  1. Make sure the working tree is clean and you're on main, up to date with origin/main.
  2. Confirm tests and type checks pass:
    poetry run pytest
    poetry run mypy src
    
  3. Preview the version bump before doing it for real:
    poetry run cz bump --dry-run
    
    This inspects Conventional Commits history since the last tag to decide patch/minor/major. Confirm the proposed version looks right.
  4. Run the real bump (updates version in pyproject.toml, updates changelog, commits, and creates the vX.Y.Z tag):
    poetry run cz bump
    
  5. Confirm with the user before pushing. Pushing tags/commits is a shared-state action:
    git push origin main --tags
    
  6. Build the distributable if needed:
    poetry build
    

Don't

  • Don't manually edit the version number anywhere. It's commitizen's job.
  • Don't force-push or delete/re-tag an already-pushed version tag.
  • Don't skip the dry run. A stray feat:/fix!: commit in history can cause a bigger bump than expected.
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.

  1. 2mo ago First seen · 49 lines · 45 tokens per session scan A c2920bd5b066

Subscribe to this mod's changes

release is a skill published in the GitHub repository andrianllmm/renux (72 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 403 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

project-graveyard

Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…

Shubhamsaboo/awesome-llm-apps · 127 tokens

mem0-test-integration

Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…

mem0ai/mem0 · 207 tokens

marimo-pair

Work inside the user's live marimo notebook from the code editor: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes through code mode. Use whenever you create, analyze, or improve the user's marimo notebook.

marimo-team/marimo · 57 tokens

cli-release

Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery. Use when a contributor asks to build a CLI beta, publish or promote a stable CLI version…

ComposioHQ/composio · 95 tokens

config-loading-precedence

How Xberg resolves config: CLI and server/MCP precedence, file walk-up, inline JSON, overrides. Use when adding a setting or one does not take effect.

xberg-io/xberg · 34 tokens

python-release

Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.

ComposioHQ/composio · 53 tokens