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/dryvist/claude-code-plugins/promote-releasenpx skills add dryvist/claude-code-plugins --skill promote-releasegit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWhat 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.00071 | $0.01785 |
| Opus 5 | $0.00036 | $0.00892 |
| Sonnet 5 | $0.00014 | $0.00357 |
| Haiku 4.5 | $0.00007 | $0.00178 |
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 3d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Promote Release
Promotes develop to main on a git-flow repo: opens (or reuses) a
develop → main PR, waits for it to go green, then merges it with a merge
commit. This is the only sanctioned way to move code into main on a
git-flow repo outside a hotfix/* PR.
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. Never
--squash, never--rebase.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 number or write CHANGELOG entries yourself —
release-please owns both once this PR lands on
main. release/*stabilization branches are out of scope here — use this skill only for the ordinarydevelop→mainpromotion.- Strongly prefer a manual end-to-end validation of
developbefore promoting — see Step 2. CI re-runs the repo's automated checks on the promotion PR; it does not replace an actual build/deploy/converge of the real artifact.
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: Manual End-to-End Validation (strongly recommended)
Before opening or merging the promotion PR, strongly prefer running the
target repo's actual end-to-end build/deploy/converge command against
develop — whatever that repo's own CLAUDE.md/AGENTS.md, README, or CI
defines as the real validation for its riskiest class of change, not just
its unit-test or lint suite. The promotion PR's own CI re-runs the repo's
automated checks anyway; this step exists to catch what CI cannot — an
actual live convergence, a real deploy, an interactive smoke test.
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.
- 3d 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 3d ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,785 once invoked, about $0.0004 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-31.
Other skills, from other repositories
push-release
Push to GitHub and optionally bump version to trigger PyPI release.
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release
Cut a new SlackCLI release end to end — survey commits since the last tag, recommend a SemVer bump, open the release issue, prepare the version bump and CHANGELOG promotion on a branch, open the linked PR, and after merge push the annotated tag that publishes binaries and updates the Homebrew tap. Use when asked to…
v1-milestone
Factory line for executing one milestone of the HAR v1.0.0 refactor (epic os-factory/har#225) — plan the wave of parallel subagents, implement each issue in its own HAR slot, ship stacked PRs, run the fixture-e2e milestone gate, and hand off for review. Use when asked to "run the next v1 milestone", "work on v1.0.0"…
finalize
Finalize orphaned recordings - stop processes, compress, push to orphan branch. TRIGGERS - finalize recording, stop asciinema, orphaned recording.