Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JansenAnalytics/claudexnpx agentmods add skills/jansenanalytics/claudex/release-managerWrote 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/jansenanalytics/claudex/release-manager)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/release-manager"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/release-manager.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.00025 | $0.00661 |
| Opus 5 | $0.00013 | $0.00331 |
| Sonnet 5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
release-manager 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-manager
Manage releases: semantic versioning, changelog generation, GitHub releases, git tags, version bumping.
When to Use
- Creating releases or preparing for a release
- Generating changelogs from git commit history
- Bumping version numbers (major/minor/patch)
- Tagging releases in git
- Publishing GitHub releases via
ghCLI
Scripts
changelog-gen.sh
Generate a changelog from git commits using conventional commit format.
bash scripts/changelog-gen.sh --since v1.0.0
bash scripts/changelog-gen.sh --since v1.0.0 --output CHANGELOG.md
bash scripts/changelog-gen.sh --since HEAD~20 --format json
Arguments:
--since <tag|commit>— Starting point (default: last tag)--output <file>— Write to file instead of stdout--format markdown|json— Output format (default: markdown)
Groups commits into: Features, Bug Fixes, Breaking Changes, Other. Falls back to listing all commits if no conventional commits found.
version-bump.sh
Bump semantic version in project files.
bash scripts/version-bump.sh --bump patch
bash scripts/version-bump.sh --bump minor --commit
bash scripts/version-bump.sh --bump 2.0.0
bash scripts/version-bump.sh --dry-run
Arguments:
--bump major|minor|patch|<version>— What to bump (required)--commit— Git commit + tag after bumping--dry-run— Show what would happen without changing anything
Detects version from: package.json, pyproject.toml, Cargo.toml, VERSION file.
gh-release.sh
Create a GitHub release using the gh CLI.
bash scripts/gh-release.sh --version v1.2.0
bash scripts/gh-release.sh --version v1.2.0 --notes "Release notes here"
bash scripts/gh-release.sh --version v2.0.0-rc.1 --prerelease --draft
Arguments:
--version <version>— Version/tag to release (required)--notes <text>— Release notes (default: auto-generate from changelog)--draft— Create as draft--prerelease— Mark as pre-release
References
semver-guide.md— Semantic versioning rules, conventional commits specrelease-checklist.md— Pre-release checklist
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 · 88 lines · 25 tokens per session scan A 8accd4d65cb6
release-manager is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 661 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-09-03.
Other skills, from other repositories
Release Engineering
Semantic versioning, changelog generation, and release/hotfix management so releases are predictable and reversible.
release-deploy
Release and deploy via GitHub tags and GitHub Actions (not every commit). Creates production releases from main and beta releases from staging using the GitHub CLI. Use when the user asks to release, ship, deploy, cut a version, tag a release, publish beta/production, create a GitHub Release, or bump a semver tag. On…
changelog
Generate or update a CHANGELOG.md in Keep a Changelog format from real git history. Use when cutting a release, tagging a version, or asked "what changed since…".
release-manager
A release-management tool for calculating semantic versions, generating changelogs and release notes, creating tags, and preparing releases. Semantic versioning uses version numbers to describe the scale of changes.
create-pr
Generate pull request descriptions, changelogs, and PR templates from git changes.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.