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 skills add dryvist/claude-code-plugins --skill promote-releasegit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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.
[](https://agentmods.dev/skills/dryvist/claude-code-plugins/promote-release)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/promote-release"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/promote-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.
<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/promote-release"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/promote-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00071 | $0.01619 |
| Opus 5.5 | $0.00028 | $0.00648 |
| Sonnet 5.5 | $0.00014 | $0.00324 |
| Haiku 4.5 | $0.00007 | $0.00162 |
Grade A, and why
promote-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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Promote Release
On pushes to develop, release-please keeps one release-please--* PR open
against develop for the version, CHANGELOG, and release notes; it does not
tag at that point. That PR is set to auto-merge and merges itself when its
checks pass. This skill confirms it merged, validates develop, then promotes
develop to main with a merge commit. Release-please tags and releases the
release commit after promotion to main.
State warning: PR status, CI, and branch state change between invocations. Re-run every git/gh command from Step 0.
Critical Rules
- Merge commit only for
develop→main. Never squash or rebase the promotion PR —main's ruleset bans both. See /gh-cli-patterns Canonical Default-Branch Detection. - This skill does not run on trunk repos. Step 0 refuses immediately if
the repo's default branch is
main. - Never invent a version, write CHANGELOG entries, create a release PR, or tag
by hand. Release-please prepares the release on
developand tags the promoted commit onmain. release/*stabilization branches are out of scope for this workflow.
Step 0: Confirm Git-Flow Repo
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')
If DEFAULT_BRANCH != develop, abort:
"This repo's default branch is
{DEFAULT_BRANCH}, notdevelop— it is not on the git-flow model. There is no develop → main promotion step here; use/merge-prfor ordinary PRs into{DEFAULT_BRANCH}."
Step 1: Sync Develop
git fetch origin --force develop main
git log --oneline origin/main..origin/develop # commits this promotion will carry
If the list is empty, stop and report: "develop has no commits ahead of
main — nothing to promote."
Step 2: Merge In-Flight Develop PRs
Drive in-flight PRs targeting develop to merged before starting the freeze.
Use /finalize-pr <PR_NUMBER> followed by /merge-pr <PR_NUMBER>; use
/pr-sweep when there are many. Do not start the freeze while PRs owned by
this session are mid-flight.
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.
- 6d ago Changed · +27 lines c90e668c16ab
- 8d ago Changed adf9fbe75204
- 13d ago Changed · -2 lines be095c084f01
- 26d ago Changed 3dced74a4eeb
- 1mo ago Changed · -34 lines 46596323b32e
- 1mo ago First seen · 161 lines · 71 tokens per session scan A b512a876d3fd
promote-release is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 1,619 once invoked, about $0.0003 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.
Other skills, from other repositories
github-ops
GitHub remote operations and README authoring: repo creation, metadata, releases, issue/PR management with preview-before-send, README as a landing page (badge row, features-as-benefits, screenshots, Recent Updates), and read-only security auditing. Triggers on: write a README, improve the README, README badges…
ci-cd-ops
CI/CD pipeline patterns with GitHub Actions, release automation, and testing strategies. Use for: github actions, workflow, CI, CD, pipeline, deploy, release, semantic release, changesets, goreleaser, matrix, cache, secrets, environment, artifact, reusable workflow, composite action.
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
release-and-changelog
Use when cutting a release, bumping a version, or writing release notes. Activate for keywords like "release", "version bump", "changelog", "release notes", "tag", "publish", "ship a release", "v1.x", "v2.x". Enforces version hygiene: SemVer respect, changelog discipline, atomic commits, tagged release. Always reflect…
releasekit
Cut a release from the Conventional Commits a repo already writes: derive the semver bump and a changelog from the commit range, bump the manifest, tag it, and publish a GitHub release, all behind a mandatory preview. Use when the user says "cut a release", "tag a version", "release this", "what's the next version"…
git-ops
Git + worktree orchestrator: status survey, per-worktree triage, commits, PRs, branches, releases, rebases — reads inline, writes to a background agent. Triggers on: git status, anything to commit, anything to push, commit, push, create PR, rebase, release, tag, changelog, worktree, land worktrees.