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.
npx agentmods add skills/delexw/claude-code-trace/cut-releasenpx skills add delexw/claude-code-trace --skill cut-releasegit clone --depth 1 https://github.com/delexw/claude-code-traceWhat 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 | $0.00211 | $0.01422 |
| Opus 5 | $0.00105 | $0.00711 |
| Sonnet 5 | $0.00042 | $0.00284 |
| Haiku 4.5 | $0.00021 | $0.00142 |
Grade A, and why
cut-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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cut-release — 98% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a Release — claude-code-trace
Turns "we should release this" into a tagged, pushed, pipeline-triggered, publicly published release with a curated CHANGELOG, in a way that survives the project's strict pre-commit hook chain and stays honest about what's actually shipping.
The skill is project-local because the steps depend on this repo's specific shape (three
version files, two lockfiles, GH Actions release on v* tag, the spec-drift +
test-reflection pre-commit hook pair).
Operating mode
The skill is fully automated end-to-end and fully synchronous. It never calls
AskUserQuestion, never waits for "yes", never branches on user preference, and
never runs any command in the background. Every Bash invocation runs in the
foreground so the session holds continuously from Phase 1 through Phase 9 — no
run_in_background: true, no trailing &, no nohup, no disown. This includes
long-running steps like gh run watch in Phase 7; set the Bash timeout parameter to
match the expected duration (e.g. 1800000 ms for the release pipeline) rather than
detaching.
Defaults are deterministic:
- Scope — always linear: every commit since
git describe --tags --abbrev=0ships. - Bump tier — highest conventional-commit tier in the subset (see
${CLAUDE_SKILL_DIR}/references/conventional-commits.md).BREAKING CHANGE:or!:produces a minor bump while the version is0.X.Y(pre-1.0 caveat) and a major bump otherwise; the skill never silently promotes to 1.0.0. - CHANGELOG — every Added/Fixed bullet is written from commit subjects + diff reads;
chore:/docs:/test:/ci:are always skipped. - Push order — tag first, then main (so CI sees the tag immediately; main catches up after).
The skill aborts (loudly) only on hard preconditions that would corrupt the release:
- Duplicate version — the proposed
vX.Y.Ztag already exists onorigin. Abort withError: vX.Y.Z already exists on origin (commit <sha>). Refusing to release the same version twice.The user must delete the remote tag intentionally if they want a re-release, or bump again. - Dirty working tree — uncommitted changes the skill didn't create. Abort with a list of dirty files.
npm run checkfails — abort and surface the failure verbatim.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/changelog-template.md 3.6 KB
- references/conventional-commits.md 3.0 KB
- references/project-shape.md 4.0 KB
- steps/phase1-inspect-and-scope.md 2.7 KB
- steps/phase2-build-release-branch.md 1.2 KB
- steps/phase3-bump-versions.md 1.7 KB
- steps/phase4-changelog.md 2.6 KB
- steps/phase5-verify-commit-tag.md 3.0 KB
- steps/phase6-push-tag.md 1.4 KB
- steps/phase7-publish-github-release.md 3.6 KB
- steps/phase8-back-to-main.md 2.1 KB
- steps/phase9-cleanup.md 1.2 KB
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.
- 2d ago First seen · 124 lines · 211 tokens per session scan A b4d239495ac7
cut-release is a skill published in the GitHub repository delexw/claude-code-trace (350 stars, last pushed 3d ago), licensed MIT. It adds 211 tokens to every session and 1,422 once invoked, about $0.0011 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-08-30.
Other skills, from other repositories
cut-release
Cuts a new versioned release of codex-trace end-to-end without asking any questions. Detects commits since the last ancestral tag, classifies them with conventional-commit rules to pick the semver bump, bumps every version-bearing file in sync, writes the CHANGELOG entry, commits and tags on a release branch, pushes…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…