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 commands/hmj1026/dhpk/create-releasegit clone --depth 1 https://github.com/hmj1026/dhpkWhat 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.00028 | $0.00481 |
| Opus 5 | $0.00014 | $0.00241 |
| Sonnet 5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
create-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 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.
What it actually says
Context
- Current version: !
jq -r '.version // .project.version // empty' package.json composer.json .claude-plugin/plugin.json 2>/dev/null | head -1 - Has RELEASE.md: !
test -f RELEASE.md && echo yes || echo no - Branch: !
git rev-parse --abbrev-ref HEAD - Status: !
git status --short - Recent tags: !
git tag --sort=-v:refname | head -5
Task
Follow the release-creator skill workflow:
- Resolve config: If a root
RELEASE.mdexists, follow it; else auto-detect the ecosystem (via the skill'sreferences/release-presets.md) to resolve version file(s), validate command, and branch model. Confirm with the user. - Verify environment: Ensure on the resolved base branch, clean status, and pulled latest.
- Version Bump: Bump version to
<version>in the project's manifest(s) — all in lockstep if there are several. - Changelog: Add a section to the project's changelog detailing changes since last tag.
- Validation: Run the project's validation/test command to ensure everything is correct.
- PR & Tag: Create the direct
develop → mainRelease PR, stop for the human merge gate, then pullmainand create the immutable annotated tag only after the merge.
Arguments:
<version>: Semver version number to release (e.g.0.28.3)--execute: Perform the preparation and post-merge mechanical phases, but never self-merge the Release PR.
Output
Either a step-by-step interactive guidance to cut the release, or the executed release flow if --execute is provided.
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 · 36 lines · 28 tokens per session scan A 24efd28e17d5
create-release is a command published in the GitHub repository hmj1026/dhpk (2 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 481 once invoked, about $0.0001 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 commands, from other repositories
tag
Create an annotated git tag with an auto-generated summary of changes since the last tag.
create-manifest
Create a migration manifest for a new patch, beta, rc, or minor release based on commits since the previous release.
trellis-create-manifest
Create a migration manifest for a new patch/minor release based on commits since the last release.
OpenSpec: Archive
Archive a deployed OpenSpec change and update specs.
prepare-release
Cut a release PR: changelog entry, version bumps, lockfiles. $ARGUMENTS is the new version (e.g. 0.4.0); ask for it if missing.
prepare-crate-release
Prepare one independently versioned crates.io package for release. $ARGUMENTS contains the Cargo package and new version (for example everruns-core 0.18.1). Ask for either value if missing.