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 hmj1026/dhpk --skill release-creatorgit clone --depth 1 https://github.com/hmj1026/dhpkWrote 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/hmj1026/dhpk/release-creator)<a href="https://agentmods.dev/skills/hmj1026/dhpk/release-creator"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/release-creator/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/hmj1026/dhpk/release-creator"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/release-creator.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.00064 | $0.01391 |
| Opus 5.5 | $0.00026 | $0.00556 |
| Sonnet 5.5 | $0.00013 | $0.00278 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
release-creator 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 yesterday.
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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Creator
Resolve project-specific release judgment first; delegate the fixed mechanics to the tested runner.
$SKILL_DIR denotes the physical directory containing this SKILL.md;
$PROJECT_DIR denotes the consumer project root. These are resolved path
notations, not ambient environment-variable requirements. Run the local runner
from the consumer project after the existing execution approval boundary.
Output
Return a release report containing the resolved configuration, changed version files, changelog result, validation result, runner phase, and the current merge/tag/CI gate. Stop with a blocked report when configuration is ambiguous, validation fails, the PR is not merged, or the tag-triggered workflow cannot be identified; do not infer a release success from a local edit or an unassociated CI run.
When NOT to Use
- PHP package/library publishing: use
$library-author composer. - Ordinary feature or bug commits: use
$git-smart-commit. - The integration branch or required tests are not ready.
1. Resolve release config
- Follow project
RELEASE.mdwhen present. - Otherwise inspect the relevant manifests and
references/release-presets.md. - Confirm these values with the user before execution:
| Token | Meaning | Typical default |
|---|---|---|
{VERSION_FILES} |
Lockstep version files | package.json |
{VALIDATE_CMD} |
Required validation | npm test |
{BASE_BRANCH} |
Integration branch | main or develop |
{RELEASE_BRANCH} |
Published branch | main |
{TAG_PREFIX} |
Tag prefix | v |
{CHANGELOG} |
Changelog file | CHANGELOG.md |
{RELEASE_WORKFLOW} |
Tag-triggered CI workflow | release.yml |
2. Author the release content
- Update every
{VERSION_FILES}entry to<version>in lockstep. - Add the release notes at the top of
{CHANGELOG}using the exact heading format required byRELEASE.md/CI. - Run
{VALIDATE_CMD}and stop on failure. - Confirm the workspace now contains only the intended release edits.
What ships with it
33 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 281 B
- distribution.yaml 2.3 KB
- references/dhpk-deploy-list/agents/openai.yaml 223 B
- references/dhpk-deploy-list/config.sh.example 789 B
- references/dhpk-deploy-list/distribution.yaml 1.6 KB
- references/dhpk-deploy-list/evals/evals.json 1.1 KB
- references/dhpk-deploy-list/evals/generic/expected/expected-fixture-01-php-yii.txt 679 B
- references/dhpk-deploy-list/evals/generic/expected/expected-fixture-02-laravel.txt 795 B
- references/dhpk-deploy-list/evals/generic/expected/expected-fixture-03-node.txt 772 B
- references/dhpk-deploy-list/evals/generic/expected/expected-fixture-04-python.txt 838 B
- references/dhpk-deploy-list/evals/generic/expected/expected-fixture-05-generic.txt 571 B
- references/dhpk-deploy-list/evals/generic/expected/expected-fixture-07-anchor-mode.txt 624 B
- references/dhpk-deploy-list/evals/generic/fixtures/fixture-01-php-yii.sh 1.8 KB runs code
- references/dhpk-deploy-list/evals/generic/fixtures/fixture-02-laravel.sh 2.0 KB runs code
- references/dhpk-deploy-list/evals/generic/fixtures/fixture-03-node.sh 1.6 KB runs code
- references/dhpk-deploy-list/evals/generic/fixtures/fixture-04-python.sh 1.8 KB runs code
- references/dhpk-deploy-list/evals/generic/fixtures/fixture-05-generic.sh 1.4 KB runs code
- references/dhpk-deploy-list/evals/generic/fixtures/fixture-07-anchor-mode.sh 2.5 KB runs code
- references/dhpk-deploy-list/i18n/en.sh 1.4 KB runs code
- references/dhpk-deploy-list/i18n/zh-TW.sh 1.6 KB runs code
- references/dhpk-deploy-list/presets/generic.sh 1.4 KB runs code
- references/dhpk-deploy-list/presets/laravel.sh 2.6 KB runs code
- references/dhpk-deploy-list/presets/node.sh 2.7 KB runs code
- references/dhpk-deploy-list/presets/php-yii.sh 2.7 KB runs code
- references/dhpk-deploy-list/presets/python.sh 2.5 KB runs code
- references/dhpk-deploy-list/references/extended-presets.example/php-yii-acmeshop.sh 7.7 KB runs code
- references/dhpk-deploy-list/references/presets.md 7.9 KB
- references/dhpk-deploy-list/references/why-this-grouping.md 5.4 KB
- references/dhpk-deploy-list/scripts/check-golden.sh 3.1 KB runs code
- references/dhpk-deploy-list/scripts/deploy-list.sh 18 KB runs code
- references/dhpk-deploy-list/SKILL.md 11 KB
- references/release-presets.md 2.4 KB
- scripts/release-runner.sh 9.3 KB runs code
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.
- yesterday Changed · +2 lines 368e92185c58
- 22d ago Changed · +3 lines 9f3a1689cb59
- 23d ago First seen · 121 lines · 64 tokens per session scan A f61c9204ddb6
release-creator is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 1,391 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-09-24.
Other skills, from other repositories
ops-ship
OPS on-demand: This skill should be used when the user asks to "ship ops plugin", "merge all PRs and…
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
pipeline-digest
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, and which branches went stale, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship"…
npm-publish
A setup guide for automatically publishing an npm package through GitHub Actions to npmjs.com. npmjs.com is a registry where JavaScript packages are shared, and GitHub Actions runs automated tasks from a repository.
project-standard-release
Prepare and ship an Agent Atelier release. Bumps the semver version in the lockstep manifests (package.json, every plugins//.claude-plugin/plugin.json, every .claude-plugin/marketplace.json plugins[] entry), updates CHANGELOG.md (Keep a Changelog format, creates it if missing), creates an annotated git tag on main…
merge-queue-thrash-stop-inflow-and-open-prs-as-drafts
When main moves faster than the slowest CI leg, every open branch goes stale before it can merge and the whole queue jams with nothing red. Use when: (1) several PRs sit at mergeStateStatus BEHIND with auto-merge armed and none of them lands; (2) branches are being updated, re-running CI and going stale again before…