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/index)<a href="https://agentmods.dev/commands/hmj1026/dhpk/index"><img src="https://agentmods.dev/badge/commands/hmj1026/dhpk/index/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/index"><img src="https://agentmods.dev/badge/commands/hmj1026/dhpk/index.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.00017 | $0.01140 |
| Opus 5.5 | $0.00007 | $0.00456 |
| Sonnet 5.5 | $0.00003 | $0.00228 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
INDEX 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commands Index (dhpk plugin)
Navigation for slash commands shipped by the dhpk plugin. dhpk commands are invoked as
/dhpk:<name>. External OpenSpec commands, when that separate plugin is installed, use/opsx:<name>.
工作入口與交付
| Command | 用途 |
|---|---|
/dhpk:flow-guide / /dhpk:flow-drive |
唯讀 usage discovery、路由與已確認工作的 explicit-only 實作 front door。 |
/dhpk:deep-analyze |
深入分析提案並產出 roadmap。 |
/dhpk:opsx-apply-resume |
長時間 opsx:apply 的 context handoff。 |
Review、測試與驗證
| Command | 用途 |
|---|---|
/dhpk:tdd-workflow test-generation |
使用保留的 TDD skill 產生測試；review 使用 change-verdict 的 tests mode。 |
/dhpk:change-verdict --mode tests --coverage |
使用保留的唯讀 review skill 檢查 coverage。 |
/dhpk:precommit / /dhpk:verify |
提交前或完整驗證。 |
$change-verdict deps |
依賴安全風險唯讀稽核；明確要求 deps fix 才進行限定修正。 |
$change-verdict pending |
針對指定路徑或目前 diff 派遣 code-reviewer 進行唯讀審查。 |
Git、發布與工作區
| Command | 用途 |
|---|---|
/dhpk:smart-commit / /dhpk:create-pr |
分組提交與建立 PR。 |
/dhpk:create-release |
版本、changelog、PR、tag 與 CI 的 release 流程。 |
/dhpk:git-worktree |
管理平行 worktree。 |
/dhpk:merge-prep / /dhpk:pr-summary |
合併前分析與 open PR 摘要。 |
Harness、文件與設定
| Command | 用途 |
|---|---|
/dhpk:update-docs / /dhpk:update-codemaps / /dhpk:doc-refactor |
更新、產生或精簡文件；update-docs 以實作證據與 writing-for-agents 契約為準。 |
/dhpk:project-brief |
將技術內容整理為 PM/CTO 摘要。 |
/dhpk:setup |
設定 plugin；用 --install hooks|rules|scripts|all 安裝資產。 |
專用工具
| Command | 用途 |
|---|---|
/dhpk:matrix-cell-onboard |
為多 major library CI matrix 新增 cell。 |
/dhpk:ui-ux-verify |
比對 OpenSpec spec 與實際 UI 渲染。 |
/dhpk:simplify |
收尾式重構簡化。 |
呼叫約定
The former review aliases are retired without forwarding aliases. Use the
read-only change-verdict skill with its code, pr, security, tests,
docs, or risk mode. Test generation uses the retained
tdd-workflow test-generation capability. The default Claude
discovery artifact is the common collection from manifests/install-profiles.json;
public profiles are retired. Use flow-guide help <skill> for
output and stop-condition metadata. Coverage review uses
change-verdict --mode tests --coverage.
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 3acb07d02944
- 17d ago Changed · -5 lines 763b77ee3b7e
- 1mo ago Changed · +2 lines fb88dd77815b
- 1mo ago Changed · +1 lines 82a4fb73719e
- 1mo ago Changed fda6087c4b31
- 1mo ago Changed · +14 lines 6c95b3449b01
- 1mo ago First seen · 73 lines · 17 tokens per session scan A a1fc931eaa0c
INDEX is a command published in the GitHub repository hmj1026/dhpk (2 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 1,140 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
init
A setup command for connecting an existing project to Octopus, a workflow built around OpenSpec project specifications and tracked changes. It checks the required command-line tool and project structure, surveys the codebase, and creates an Arena handover report.
review
A read-only review command that asks a reviewer agent to examine a branch or the current uncommitted changes. It returns a four-part acceptance report, including high-risk changes and whether the work matches a supplied specification.
review
Comprehensive multi-agent code quality and architecture review with cross-validation.
config
View and configure Argus settings.
welcome
Welcome to Argus - getting started guide.
checklist
Generate a custom checklist for the current feature based on user requirements.