agentmods.dev

release

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

In plain words
What is it for?
Use it for patch, minor, major, or explicitly numbered releases, including version changes, builds, npm publishing, commits, and pushes.
Why use it?
It turns the release checklist into a repeatable process and stops when the build or publishing step fails.

Command for Claude Code

11 3mo ago A scan 16 tokens original MIT
View the source file fvckprth/remediate
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.

agentmods
npx agentmods add commands/fvckprth/remediate/release
Clone the repo
git clone --depth 1 https://github.com/fvckprth/remediate

Made for: Claude Code.

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 819 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00016 $0.00819
Opus 5 $0.00008 $0.00409
Sonnet 5 $0.00003 $0.00164
Haiku 4.5 $0.00002 $0.00082

Measured 2d ago against content hash 428b3aa8c76b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

.claude/commands/release.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 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

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

  2. bump version in package/package.json

  3. build the package

    • pnpm run build from the repo root
    • if it fails, stop and report

  4. 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

  5. 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)

  6. update the marketing site (single commit, three file edits)

    • file 1: /Users/parthpatel/Desktop/Projects/remediate-mktg/src/components/nav-config.tsx
      • update the VERSION constant
    • file 2: /Users/parthpatel/Desktop/Projects/remediate-mktg/package.json
      • bump "remediate": "^X.Y.Z"
    • file 3: /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 · 53 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. 2d 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 (11 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 819 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-08-30.

DevOps and cloudGit and workflow
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens