A release checklist for publishing a new version of Remotion packages to npm, the JavaScript package registry. It includes authentication, building, versioning, testing an example, and creating a publish token.

Use it to prepare and publish a Remotion release, update its version, run the example deployment check, and configure npm publishing access.

It makes the package-release sequence explicit and stops the process when required build or test steps fail.

release — Command for Claude Code by MoizIbnYousaf/marketing-cli

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.

Clone the repo

git clone --depth 1 https://github.com/MoizIbnYousaf/marketing-cli

Made for: Claude Code.

Or install marketing-cli, the plugin that ships this one along with the rest of its 90 skills, 9 commands, 1 hook, 2 MCP servers.

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/moizibnyousaf/marketing-cli/release/github.svg)](https://agentmods.dev/commands/moizibnyousaf/marketing-cli/release)

Your own site

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

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

When invoked 676 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.00000	$0.00676
Opus 5.5	$0.00000	$0.00270
Sonnet 5.5	$0.00000	$0.00135
Haiku 4.5	$0.00000	$0.00068

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

skills/remotion-best-practices/references/upstream-internal/commands/release.md · 24 lines

What it actually says

Kill any turbo processes that might be running with SIGKILL
Run npm login (I will manually do 2FA in the browser)
Use op item get "Npmjs" --fields password --reveal --account remotiondev.1password.com to get the password for NPM.
Use op item get "Npmjs" --otp --account remotiondev.1password.com to get a one-time password for 2FA.
Run npm token create --name="PublishRemotionXXXXXX" --packages "remotion" --packages "create-video" --packages-and-scopes-permission read-write --bypass-2fa --scopes "@remotion" --otp=<otp>. Replace XXXXXX with a random string so we have a unique name. Use op item get "Npmjs" --otp --account remotiondev.1password.com to get the OTP and pass it via --otp=. It will ask for a password, pipe in the password using echo "$PASSWORD" |.
Run bun i
Run bun run build
Run npm view remotion version to get the current version number
Run bun set-version.ts <version>, where is the current version plus 1. If the exit code is not 0, abort the entire release process immediately.
Run cd packages/example && sh runlambda.sh && cd ../... If this fails, abort the release.
Run NPM_CONFIG_TOKEN=<token> bun run release where is the NPM token we just created
Generate a changelog in markdown and save it to /tmp/release-<version>.md:
- Run git log v<previous_version>..v<new_version> --oneline to get all commits
- Extract PR numbers from merge commits
- For each PR, run gh pr view <number> --json title,author,number,url --jq '"* \(.title) by @\(.author.login) in \(.url)"'
- Categorize PRs into sections: "What's Changed", "Templates", "Docs", "Internal"
- In "What's Changed", sort items so that entries for the same package are adjacent (no subheadings, just sorted order). Changes to the remotion core package should appear first
- Strip redundant prefixes from PR titles (e.g. remove "Docs:" from items in the Docs section)
- "Templates" is a separate section for any template-* changes
- Check for genuinely new contributors by running gh api repos/remotion-dev/remotion/contributors --paginate --jq '.[].login' and comparing against PR authors. Only add a "New Contributors" section for authors not in that list
- Add **Full Changelog**: https://github.com/remotion-dev/remotion/compare/v<previous_version>...v<new_version> at the bottom
- Use the same format as previous GitHub releases (check with gh release view v<previous_version>)
- Don't release until you get approval. Allow me to edit it before.

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 First seen · 24 lines · 0 tokens per session scan A 89c3d8ff0b88

Subscribe to this mod's changes

release is a command published in the GitHub repository MoizIbnYousaf/marketing-cli (32 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 676 tokens. 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.

Claude Code Git and workflow Releases agent-skills ai-agents ai-marketing brand-voice claude-code-skills

release

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

release

release

bump-version

upgrade

versione

create-pr