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/aldianriski/lean-flow/release-patchnpx skills add aldianriski/lean-flow --skill release-patchgit clone --depth 1 https://github.com/aldianriski/lean-flowWhat 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.00093 | $0.01525 |
| Opus 5 | $0.00046 | $0.00763 |
| Sonnet 5 | $0.00019 | $0.00305 |
| Haiku 4.5 | $0.00009 | $0.00153 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-patch
Patch-release orchestrator. Auto-detects the project type via a manifest cascade. The last step is a hard human gate before push — this skill never pushes.
When to invoke
- A bug fix or hotfix has landed and you need a PATCH bump + changelog.
Do not use for MINOR (new feature/skill) or MAJOR (breaking) bumps — those are governance decisions; bump those manifests by hand with an explicit changelog entry.
At sprint close the close step routes here only for a fixes-only sprint (PATCH); a sprint that
shipped new capabilities is a MINOR by-hand bump (it scans plan_commit..HEAD to tell — see step 1).
Mode-detection cascade
First match wins. Priority: plugin > npm > python > cargo > go > flat.
| Detected file | Mode | Bump target |
|---|---|---|
.claude-plugin/plugin.json |
plugin | lockstep with marketplace.json (both must stay equal) |
package.json |
npm | version field |
pyproject.toml |
python | [project] or [tool.poetry] version |
Cargo.toml |
cargo | [package] version |
go.mod |
go | tag-based — prompt the user for the tag string |
VERSION (flat file) |
flat | overwrite with the new semver |
| none of the above | changelog-only | no manifest — prepend a dated CHANGELOG entry, no version bump (see below) |
Steps
- Diff scan —
git diff --name-only HEAD~1 HEAD(orHEADif uncommitted). At sprint close → scan the whole sprint rangeplan_commit..HEAD(readplan_commitfrom the just-closed sprint frontmatter) — else a multi-commit sprint is misjudged by its docs-only close commit. If every changed path is underdocs/, abort:[skip] docs-only diff — no version bump. Exit. - Mode detect — run the cascade; save the mode + manifest path(s). No manifest → changelog-only mode (below); do not exit.
- PATCH bump — increment the patch digit per mode. Plugin: verify both files are equal, then bump both. Single-manifest modes: read → bump → write. Go: prompt for the tag string.
- CHANGELOG entry — detect root
CHANGELOG.md(canonical placement, STANDARD §2, ADR-012), else legacydocs/CHANGELOG.md/CHANGES.md/HISTORY.md(default rootCHANGELOG.md). Prepend a new block matching the file's existing entry shape; if empty/missing, use Keep-a-Changelog format. - Stale-doc clear — any doc with
last_updated:frontmatter that appears in the diff → bump it to today (yyyy-MM-dd). - HARD STOP — push gate — emit the message below and exit (if
docs/deployment/deployment-guide.mdexists — legacydocs/DEPLOY.mdstill matched — point to it for the push / deploy / verify / rollback steps). This skill never invokesgit push.
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.
- 2d ago First seen · 99 lines · 93 tokens per session scan A 06206a1a36e7
release-patch is a skill published in the GitHub repository aldianriski/lean-flow (4 stars, last pushed 3d ago), licensed MIT. It adds 93 tokens to every session and 1,525 once invoked, about $0.0005 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX,校验 sha256,从 Release body 生成 Store listing releaseNotes 预览,并输出手动上传指引。.