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/update-docsgit 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/update-docs)<a href="https://agentmods.dev/commands/hmj1026/dhpk/update-docs"><img src="https://agentmods.dev/badge/commands/hmj1026/dhpk/update-docs.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.01776 |
| Opus 5 | $0.00009 | $0.00888 |
| Sonnet 5 | $0.00003 | $0.00355 |
| Haiku 4.5 | $0.00002 | $0.00178 |
Grade A, and why
update-docs 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 today.
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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dhpk:update-docs
Contract
Use this command after a public workflow, route, setup, distribution, or configuration change makes a document stale. It may also be invoked with a document path or workflow keyword for a bounded refresh. It updates Markdown and other documentation only; it does not edit application source, tests, the route table, or generated runtime projections.
Do not use it for codemap generation (/dhpk:update-codemaps), a policy or
link/frontmatter review (change-verdict in docs mode), or
external-library research (docs-lookup). The doc-updater agent owns the
same contract when structural changes require a proactive handoff; this command
is its user-facing entry point.
Read the nearest policy before editing:
docs/agent-guidance/writing-for-agents.mddefines pointer, hierarchy, completion, pruning, and boundary checks.docs/agent-guidance/command-contract.mddefines command-level evidence and handoff expectations.rules/execution-policy.mdowns dispatch, reviewer, and dirty-worktree boundaries.
The implementation and distribution SSOT map is:
| Fact | Prefer this owner |
|---|---|
| Public names, surfaces, counts | manifests/distribution-inventory.json |
| Route matching and invocation class | skills/flow-guide/references/route-table.json and skills/flow-guide/scripts/route-result.js |
| Effective configuration | docs/configuration.md and its Traditional Chinese pair |
| Install, update, migration, rollback | docs/platform-installation.md, docs/skill-platform-migration.md |
| Runtime workflow, receipts, and gate outcomes | docs/harness-workflow.md and the owning harness scripts |
| Agent-writing rules | docs/agent-guidance/writing-for-agents.md |
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.
- today First seen · 164 lines · 17 tokens per session scan A 9abbc446c036
update-docs is a command published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,776 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-09-05.
Other commands, from other repositories
init
在既有專案初始化 Octopus——摸專案、檢查 OpenSpec CLI 與結構（缺則引導安裝）、盤點 change 狀態、建 Arena、出交接報告。每個專案跑一次。.
build
SDD 後半段（全自主）：驗 Locked → Builder 逐 task 實作（每條 task 隨行回報）→ 審查 → P1 自動退修（≤3 輪）→ 帶驗收報告回來，你只剩 merge 與 archive。中途不停下來等人。.
harness-lint
이 프로젝트의 생성된 하네스를 계약에 대고 검사한다. 결정적 검사 9종.
spec
SDD 前半段：需求釐清（反問+挑戰）→ OpenSpec change 一次落檔（proposal＋delta＋tasks，Draft）→ TPM 拍板鎖定（回一個 OK 即可）。鎖定後 build 全自主執行。.
debug
用 Agent 工具啟動 debugger agent，把錯誤資訊原文（含截圖/log）完整轉給它。.
review
單獨審查——Reviewer 對指定 branch/變更出四段式驗收報告（可直接貼 PR description）。.