What is make-release?

A release workflow for the Holix GitHub repository. It prepares a pull request, checks that automated tests pass, merges it, and creates the next numbered release.

Use it when you need to release a new Holix version through GitHub and publish it to PyPI, Python’s package repository.

It removes the need to remember the steps and checks required to publish a Holix release safely. It also helps keep the package version, changelog, Git tag, and GitHub release aligned.

make-release — Skill for Claude Code and Codex by javded-itres/Holix

Install

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.

Any agent

npx skills add javded-itres/Holix --skill make-release

Clone the repo

git clone --depth 1 https://github.com/javded-itres/Holix

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/javded-itres/holix/make-release/github.svg)](https://agentmods.dev/skills/javded-itres/holix/make-release)

Your own site

<a href="https://agentmods.dev/skills/javded-itres/holix/make-release"><img src="https://agentmods.dev/badge/skills/javded-itres/holix/make-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/javded-itres/holix/make-release"><img src="https://agentmods.dev/badge/skills/javded-itres/holix/make-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,161 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 warn 7 Sept 2026

SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Tool Misuse · line 110
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.

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.00077	$0.01161
Opus 5.5	$0.00031	$0.00464
Sonnet 5.5	$0.00015	$0.00232
Haiku 4.5	$0.00008	$0.00116

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

Security

Grade A, and why

make-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 1mo 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.

.grok/skills/make-release/SKILL.md · 135 lines

How it starts

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

Holix release («сделай релиз»)

When the user says сделай релиз (or equivalent), execute this pipeline end-to-end. Do not stop after the PR. Do not skip CI. Do not tag before merge.

Canonical package rules: RULES.md §8. This skill is the operational loop.

Preconditions

Repo: javded-itres/Holix. Default branch: main.
Auth: gh auth status must be logged in.
Fetch first: git fetch origin --tags.
Next version = latest GitHub release + patch (1.0.7 → 1.0.8), unless the user asked for minor/major.
Confirm versions agree before tagging:
- pyproject.toml [project].version
- cli/__init__.py __version__
- latest gh release list / git tag
Do not rsync/scp/hotfix production. Tag on main is enough: GHA GitHub Release + Publish to PyPI run from vX.Y.Z.
Run ./scripts/lint.sh (or --fix) before every push.

1) PR with the changes

Include code + version bump + changelog in the same PR so there is one merge, then a tag.

If an open PR already covers this work, reuse it and add the bump there if missing.
Otherwise branch from up-to-date origin/main: release/X.Y.Z (example: release/1.0.8).
Commit the user's uncommitted/unmerged work (no secrets, no node_modules/, no local .env).
Bump version with scripts/versioning.py (or edit both files):
- pyproject.toml
- cli/__init__.py
Update docs/CHANGELOG.md:
- Move ## Unreleased notes into ## X.Y.Z — YYYY-MM-DD
- Leave a fresh empty ## Unreleased
- Write Added/Fixed/Tests from the actual diff
Push and open PR → main:

gh pr create --base main --title "Holix X.Y.Z" --body "$(cat <<'EOF'
## Summary
Release Holix X.Y.Z.

## Checklist
- [ ] Version matches in pyproject.toml and cli/__init__.py
- [ ] docs/CHANGELOG.md has section X.Y.Z
- [ ] CI green (ruff + pytest matrix)

After merge: tag `vX.Y.Z` (creates GitHub Release + PyPI).
EOF
)"

2) GitHub tests until green

Watch GitHub Actions on the PR, not only local pytest.

Read the full file on GitHub · 135 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.

1mo ago First seen · 135 lines · 77 tokens per session scan A 4270ca235399

Subscribe to this mod's changes

make-release is a skill published in the GitHub repository javded-itres/Holix (17 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 1,161 once invoked, about $0.0003 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.

Claude Code Git and workflow Releases agent-skills ai assistant hermes hermes-agent

make-release

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Holix release («сделай релиз»)

Preconditions

1) PR with the changes

2) GitHub tests until green

What this file has done since we first saw it

Other skills, from other repositories

git-conventional-commits

github-repo-management

github-pr-workflow

github-pr-workflow

github

git-workflow