A release command that builds a package, publishes it to npm, updates its version, and deploys the related site.

Use it for patch, minor, major, or explicitly numbered releases, including version changes, builds, npm publishing, commits, and pushes.

It turns the release checklist into a repeatable process and stops when the build or publishing step fails.

How fvckprth/remediate configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to fvckprth/remediate. 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/fvckprth/remediate/main/.claude/commands/release.md

Clone the repo

git clone --depth 1 https://github.com/fvckprth/remediate

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/fvckprth/remediate/release/github.svg)](https://agentmods.dev/commands/fvckprth/remediate/release)

Your own site

<a href="https://agentmods.dev/commands/fvckprth/remediate/release"><img src="https://agentmods.dev/badge/commands/fvckprth/remediate/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/commands/fvckprth/remediate/release"><img src="https://agentmods.dev/badge/commands/fvckprth/remediate/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 808 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.

Model	Per session	Once invoked
Fable 5.1	$0.00016	$0.00808
Opus 5.5	$0.00006	$0.00323
Sonnet 5.5	$0.00003	$0.00162
Haiku 4.5	$0.00002	$0.00081

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

.claude/commands/release.md · 52 lines

How it starts

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

Release

publish a new version of remediate.

steps

determine version bump
- if $ARGUMENTS is patch, minor, or major, use that
- if $ARGUMENTS is a specific version like 0.2.0, use that exactly
- if $ARGUMENTS is empty, default to patch
- if package/package.json is already at the target version (e.g. an earlier session bumped it), skip step 2
bump version in package/package.json
build the package
- pnpm run build from the repo root
- if it fails, stop and report
publish to npm
- npm publish from package/
- if it fails, stop and report
- capture the integrity hash and tarball URL for step 6: npm view [email protected] dist.integrity dist.tarball
commit + push the widget repo
- if the working tree has uncommitted source changes that belong in this release, commit them first as a separate fix: / feat: / refactor: commit (mirrors the project's history pattern: feature commit, then version-bump commit)
- then commit the version bump alone with: chore: bump to vX.Y.Z
- if you're on a worktree branch, push with git push origin HEAD:main (fast-forwards origin/main from the worktree HEAD)
update the marketing site (single commit, two file edits)
- the displayed version is derived from package.json (src/site.ts), so there is no constant to bump
- file 1: /Users/parthpatel/Desktop/Projects/remediate-mktg/package.json
  - bump "remediate": "^X.Y.Z"
- file 2: /Users/parthpatel/Desktop/Projects/remediate-mktg/package-lock.json — hand-edit only, do NOT run npm install
  - top-level dep range: packages."".dependencies.remediate → ^X.Y.Z
  - lockfile block: node_modules/remediate → update version, resolved, integrity (use the integrity from step 4)
- CRITICAL — DO NOT run npm install remediate@latest (or similar) on macOS. npm strips cross-platform optionalDependencies (e.g. lightningcss-linux-x64-gnu) from package-lock.json when run on a single platform, and Vercel's Linux build fails with a native binary load error. Hand-editing keeps the rest of the lockfile intact.
- validate before committing:
  - node -e "JSON.parse(require('fs').readFileSync('/Users/parthpatel/Desktop/Projects/remediate-mktg/package-lock.json'))" exits 0
  - grep -c "node_modules/lightningcss-linux" /Users/parthpatel/Desktop/Projects/remediate-mktg/package-lock.json returns ≥ 2 (cross-platform deps still present)
- commit message: chore: bump version display + upgrade remediate to vX.Y.Z
- push to origin (Vercel auto-deploys)

Read the full file on GitHub · 52 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 Changed · -1 lines cee76e75dfd8
2mo ago First seen · 53 lines · 16 tokens per session scan A 428b3aa8c76b

Subscribe to this mod's changes

release is a command published in the GitHub repository fvckprth/remediate (12 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 808 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-30.

DevOps and cloud Git and workflow Releases

release next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
releasefvckprth/remediate	Command	12	1mo ago	MIT	A	16	Claude Code
landgmickel/flow-next	Command	717	yesterday	MIT	A	13	Claude Code
qualityDesko77/claude-code-skills-1c	Command	90	yesterday	MIT	A	18	Claude Code
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code
release-managerruvnet/agentic-flow	Command	838	yesterday	none	A	0	Claude Code
create-prdsswift/ion	Command	5	yesterday	MIT	A	28	Claude Code
rally-merge-prddgonzal3/rally	Command	6	3d ago	MIT	A	0	Claude Code

remediate: Command for Claude Code