Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/hmj1026/dhpknpx agentmods add skills/hmj1026/dhpk/dhpk-deploy-listWrote 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/dhpk-deploy-list)<a href="https://agentmods.dev/skills/hmj1026/dhpk/dhpk-deploy-list"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-deploy-list/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/dhpk-deploy-list"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-deploy-list.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.00151 | $0.02940 |
| Opus 5 | $0.00076 | $0.01470 |
| Sonnet 5 | $0.00030 | $0.00588 |
| Haiku 4.5 | $0.00015 | $0.00294 |
Grade A, and why
dhpk-deploy-list 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 3d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deploy-list
Generates a deploy file list from git history. All logic lives in the script — Claude parses arguments, invokes the script, and emits stdout verbatim. No post-processing.
Package surfaces
The package keeps the immutable generator in scripts/deploy-list.sh, its golden
runner in scripts/check-golden.sh, ecosystem rules in presets/, structural labels
in i18n/, and preset guidance in references/. Copy config.sh.example to a
project-local config.sh when defaults need to be pinned. The evals/ fixtures are
the regression surface for schema changes.
Arguments
| Flag | Required | Default | Notes |
|---|---|---|---|
--tag |
✅ | — | ^\[.+\]$, pure metadata, NOT used for grouping |
--description |
✅ | — | freeform text |
--deploy-commits |
⛳ | (none) | CSV of commit SHAs → union diff = main group; rest of base..head = warn group |
--anchor |
⛳ | (none) | source-code inline anchor string → rg -l --fixed-strings finds matching source files; mutually exclusive with --deploy-commits / --auto-detect-tag |
--date |
⛳ | today | YYYY/MM/DD |
--author |
⛳ | $DEFAULT_AUTHOR → $USER → user |
|
--project |
⛳ | git toplevel basename | |
--base |
⛳ | $DEFAULT_BASE → main |
git ref (ignored in anchor mode) |
--head |
⛳ | HEAD |
git ref (ignored in anchor mode) |
--preset |
⛳ | $DEFAULT_PRESET → auto-detect → generic |
see Preset selection |
--lang |
⛳ | $DEFAULT_LANG → en |
zh-TW or en |
--auto-detect-tag |
⛳ | off | grep -i -F $TAG in commit messages, fill --deploy-commits if empty |
Defaults marked $DEFAULT_* are read from config.sh if present. CLI
flags always win.
Preset selection
Resolution order (first non-empty wins):
--preset <name>CLI flag$DEFAULT_PRESETfromconfig.sh- Auto-detect (probe order, first match wins):
protected/yii.phporprotected/config/main.php+protected/views/→php-yiiartisanat root →laravelpackage.json+ nocomposer.json→nodepyproject.tomlorsetup.py→python- fallback →
generic(stderr note emitted)
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.
- 3d ago First seen · 234 lines · 151 tokens per session scan A d042c7b5c67f
dhpk-deploy-list is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed yesterday), licensed MIT. It adds 151 tokens to every session and 2,940 once invoked, about $0.0008 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-09-05.
Other skills, from other repositories
release
Release a new version of the mumei repository. Invoke when the user gives an explicit release instruction ("release it", "/release", "patch release", "ship 0.2.0"). Takes no argument or "patch" / "minor" / "major" for a SemVer bump, or a direct version such as "0.2.0". Wraps any uncommitted changes into a single…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
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).
bump-version
A procedure for changing a package and plugin version in several project files at the same time.
release-retrospective
Produce a structured look-back after a major release or deprecation — capturing what the plan got right, what it missed, and what to do differently. Trigger when someone says: release retrospective, post-release review, what went wrong with the release, how did the deprecation go, release post-mortem, retro on the…