Borrowing it
Nothing to install: this file belongs to epam/ai-dial-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/epam/ai-dial-core/development/.claude/commands/release-patch.mdgit clone --depth 1 https://github.com/epam/ai-dial-coreWrote 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/commands/epam/ai-dial-core/release-patch)<a href="https://agentmods.dev/commands/epam/ai-dial-core/release-patch"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-core/release-patch/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/commands/epam/ai-dial-core/release-patch"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-core/release-patch.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.00016 | $0.01076 |
| Opus 5.5 | $0.00006 | $0.00430 |
| Sonnet 5.5 | $0.00003 | $0.00215 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
release-patch 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 21d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a release patch
Arguments: $ARGUMENTS — first the release branch (e.g. release-0.9), then one or more merged PR numbers (e.g. 2060 2067).
development uses squash merges (<title> (#N)), so one PR is exactly one commit.
Preconditions
- Abort if fewer than 2 arguments are given.
- Abort if the working tree is dirty (
git status --porcelain --untracked-files=nois not empty); untracked files are ignored. git fetch origin --tags, then verifyorigin/{release}exists. If not, list availableorigin/release-*branches and stop.
Steps
-
Check out and update the release branch:
git checkout {release} git pull origin {release} -
Resolve commits for all PRs up front. For each PR number
{n}:gh pr view {n} --json state,mergeCommit— usemergeCommit.oidwhenstateisMERGED.- If that fails, fall back to
git log origin/development --format=%H --grep='(#{n})'. - If the PR is not merged or no commit is found, stop and report.
Sort the commits by merge order on
origin/development(oldest first, e.g.git rev-list --reverse origin/developmentfiltered to the resolved SHAs), regardless of argument order. Print the final PR → SHA order before continuing. -
Create the patch branch. Compute
{next_release_version}: takegit describe --tags --abbrev=0 origin/{release}(e.g.0.9.2) and increment the patch number (0.9.3). If no tag is found, ask the human. A previous aborted run or an open patch PR leaves the tag unchanged, so first check that the name is free locally (git rev-parse --verify --quiet patch-{next_release_version}) and on origin (git ls-remote --exit-code --heads origin patch-{next_release_version}). If either exists, ask the human whether to delete it or use a suffix (patch-{next_release_version}-2); never overwrite it. Then:git checkout -b patch-{next_release_version}Never push to the release branch directly.
-
Cherry-pick each commit in order:
git cherry-pick -x {sha}-xappends a(cherry picked from commit ...)trailer; keep the original message.
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.
- 21d ago First seen · 87 lines · 16 tokens per session scan A ae4a7643e1ab
release-patch is a command published in the GitHub repository epam/ai-dial-core (661 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 1,076 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-10-07.
Other commands, from other repositories
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
update-documentation
You are a release engineer responsible for maintaining the root-level CHANGELOG.md and verifying plugin READMEs. Analyze git changes, update the single CHANGELOG.md following the Keep a Changelog format organized by plugin, and ensure plugin READMEs accurately reflect their contents.
release
Prepara e pubblica una nuova release del plugin mcp-legal-it. Bumpa la versione in tutti i manifest, aggiorna i changelog e la description con il conteggio tool corretto, crea il release branch, merge in main e tagga.
fire-update
Check for and apply plugin updates from GitHub repository.
ship
Pre-ship pipeline — test, review, then prepare a clean commit.
rebase_prompt
You are a git rebase assistant. Your job is to rebase the current branch onto origin/ and intelligently resolve any merge conflicts that arise. The repository has already been fetched and the base branch is ; you may assume origin/ is up-to-date.