agentmods.dev

agent-xlsx: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from apetta/agent-xlsx. It costs 17 tokens per session (933 once invoked), scanned A, original, Apache-2.0.

A release command that assesses a software version change, updates release files, publishes the package to PyPI, and updates the changelog. PyPI is a public registry where Python packages are distributed.

In plain words
What is it for?
Checking the Git state, reviewing commits since the last tag, calculating a version bump, updating package versions, tagging, publishing, and updating release notes.
Why use it?
It organizes the checks needed before releasing and stops when a required step fails. It uses commit types to determine whether the version change should be major, minor, or patch.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is apetta/agent-xlsx's own configuration. It tells Claude Code how to work on agent-xlsx 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 agent-xlsx configures →

not rated 9repo 7mo ago A scan 17 tokens original Apache-2.0
View source ↗ apetta/agent-xlsx agent-xlsx.dev
Reuse

Borrowing it

Nothing to install: this file belongs to apetta/agent-xlsx. 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/apetta/agent-xlsx/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/apetta/agent-xlsx

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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/commands/apetta/agent-xlsx/release/github.svg)](https://agentmods.dev/commands/apetta/agent-xlsx/release)
Your own site
<a href="https://agentmods.dev/commands/apetta/agent-xlsx/release"><img src="https://agentmods.dev/badge/commands/apetta/agent-xlsx/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/commands/apetta/agent-xlsx/release"><img src="https://agentmods.dev/badge/commands/apetta/agent-xlsx/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 933 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.
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.00017 $0.00933
Opus 5.5 $0.00007 $0.00373
Sonnet 5.5 $0.00003 $0.00187
Haiku 4.5 $0.00002 $0.00093

Measured 2mo ago against content hash acdb894c8668, 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.

.claude/commands/release.md · 56 lines

How it starts

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

State

  • Recent commits (tagged): !git log --oneline --decorate -20
  • Latest tag: !git tag --sort=-v:refname | head -1
  • Status: !git status --short
  • Version: !grep '^version' pyproject.toml

Steps

Stop and report if any step fails.

  1. Pre-flight: Verify clean working tree and on main. If there are no commits since the last tag, report "Nothing to release" and stop.

  2. Assess bump: Analyse all commits since the last tag:

    • BREAKING CHANGE or !: in any commit → major
    • Any feat: commit → minor
    • Only fix:, chore:, docs:, refactor: → patch
    • Take the highest applicable level.
    • If $ARGUMENTS is provided and matches the assessed level, proceed.
    • If $ARGUMENTS is provided but disagrees with the assessment, flag the mismatch with reasoning and ask the user to confirm or revise.
    • If $ARGUMENTS is empty, propose the assessed bump and ask the user to confirm.

  3. Compute version: Parse current from pyproject.toml, apply bump. State old → new.

  4. Update versions in exactly these 2 files:

    • pyproject.toml → version = "X.Y.Z"
    • src/agent_xlsx/__init__.py → __version__ = "X.Y.Z"

    Grep the old version string across pyproject.toml and src/ to confirm zero remaining hits.

  5. Sync lockfile: uv sync --group dev

  6. Changelog: Add entry to docs/src/app/changelog/page.mdx below # Changelog, above the previous release entry. Review all commits since the previous tag. Follow the existing format and tone. Keep it concise; consolidate related fixes into single bullets.

  7. Validate: uv run ruff check && uv run ruff format --check && uv run ty check && uv run pytest -v

  8. Commit: Stage pyproject.toml, src/agent_xlsx/__init__.py, uv.lock, and docs/src/app/changelog/page.mdx. Commit message: chore: release vX.Y.Z

  9. Tag + push: git tag vX.Y.Z && git push origin main --tags

  10. GitHub release: Derive notes from the changelog entry. Use gh release create vX.Y.Z --title "vX.Y.Z" --notes "..." (note: the flag is --notes/-n, NOT --body).

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

  1. 2mo ago First seen · 56 lines · 17 tokens per session scan A acdb894c8668

Subscribe to this mod's changes

release is a command published in the GitHub repository apetta/agent-xlsx (9 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 933 once invoked, about $0.0001 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-31.

Git and workflowReleases
Related

release compared with commands from other repositories

release next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
releaseapetta/agent-xlsxCommand97mo agoApache-2.0A17Claude Code
landgmickel/flow-nextCommand717yesterdayMITA13Claude Code
qualityDesko77/claude-code-skills-1cCommand902d agoMITA18Claude Code
release-notesOpenHands/extensionsCommand176yesterdayMITA44Claude Code
release-managerruvnet/agentic-flowCommand838yesterdaynoneA0Claude Code
create-prdsswift/ionCommand52d agoMITA28Claude Code
rally-merge-prddgonzal3/rallyCommand63d agoMITA0Claude Code