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.
git 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/commands/hmj1026/dhpk/merge-prep)<a href="https://agentmods.dev/commands/hmj1026/dhpk/merge-prep"><img src="https://agentmods.dev/badge/commands/hmj1026/dhpk/merge-prep/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/hmj1026/dhpk/merge-prep"><img src="https://agentmods.dev/badge/commands/hmj1026/dhpk/merge-prep.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.00147 |
| Opus 5.5 | $0.00026 | $0.00059 |
| Sonnet 5.5 | $0.00013 | $0.00029 |
| Haiku 4.5 | $0.00006 | $0.00015 |
Grade A, and why
merge-prep 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 8d 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
Load the canonical $merge-prep Skill from SKILL.md and follow it with $ARGUMENTS.
Keep its argument contract, authority boundary, verification, and output.
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.
- 8d ago Changed · -1 lines 03b4c78b49f0
- 16d ago Changed · -9 lines · +45 tokens per session aabc76dc8f7d
- 1mo ago Changed · -19 lines · -5 tokens per session bf65712b888c
- 1mo ago First seen · 39 lines · 24 tokens per session scan A e193487f56e9
merge-prep is a command published in the GitHub repository hmj1026/dhpk (2 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 147 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-05.
Other commands, from other repositories
worktree
Manage git worktrees for isolated feature development.
patch-notes
Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication.
resume
Show the restored Continuity project state (frozen constraints, decisions, rejected paths, next step).
hotfix
Ship a fast branch-based P0 hotfix — diagnose, implement, open a ready-for-review PR, then verify + review after (deferred by design).
orient-commit
Draft a git commit message (what / why / findings) for review before committing.
sdlc-release
Release planning and rollout - versioning, staging, gradual deployment, rollback.