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/check-skillgit 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/check-skill)<a href="https://agentmods.dev/commands/hmj1026/dhpk/check-skill"><img src="https://agentmods.dev/badge/commands/hmj1026/dhpk/check-skill.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.00013 | $0.00435 |
| Opus 5 | $0.00006 | $0.00217 |
| Sonnet 5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
check-skill 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 4d 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
Must read and follow the skill below before executing this command:
@skills/dhpk-skill-health-audit/SKILL.md
Context
- Skills directory: !
ls skills/ | wc -lskills - Commands directory: !
ls commands/ | wc -lcommands
Task
Run skill health check.
Arguments
$ARGUMENTS
| Parameter | Description |
|---|---|
--deep |
Include manual review dimensions (Step 2) |
--json |
Output JSON format |
Workflow
Run skill-lint.js → [Optional: manual review] → Report + Gate
- Run automated lint:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/run-skill.sh" dhpk-skill-health-audit skill-lint.js --fix-hint(append--jsonif$ARGUMENTScontains--json) - If
--deep(from$ARGUMENTS): Read flagged skills and evaluate Why>What, scope, progressive loading, routing precision - Output: Health report + Gate sentinel
Output
# Skill Health Check Report
## Summary
| Metric | Value |
|--------|-------|
| Skills scanned | N |
| P0/P1/P2 | N/N/N |
## Per-Skill Results
| Skill | Routing | When-NOT | Output | Status |
|-------|---------|----------|--------|--------|
## Gate: ✅ All Pass / ⛔ N issues
Examples
/dhpk:check-skill
/dhpk:check-skill --deep
/dhpk:check-skill --json
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.
- 4d ago First seen · 68 lines · 13 tokens per session scan A 94c750bf2576
check-skill is a command published in the GitHub repository hmj1026/dhpk (2 stars, last pushed 4d ago), licensed MIT. It adds 13 tokens to every session and 435 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
init
在既有專案初始化 Octopus——摸專案、檢查 OpenSpec CLI 與結構（缺則引導安裝）、盤點 change 狀態、建 Arena、出交接報告。每個專案跑一次。.
harness-lint
이 프로젝트의 생성된 하네스를 계약에 대고 검사한다. 결정적 검사 9종.
harness-evolve
하네스를 쓴 결과를 회고하고 에이전트·스킬·오케스트레이터에 되먹인다.
build
SDD 後半段（全自主）：驗 Locked → Builder 逐 task 實作（每條 task 隨行回報）→ 審查 → P1 自動退修（≤3 輪）→ 帶驗收報告回來，你只剩 merge 與 archive。中途不停下來等人。.
spec
SDD 前半段：需求釐清（反問+挑戰）→ OpenSpec change 一次落檔（proposal＋delta＋tasks，Draft）→ TPM 拍板鎖定（回一個 OK 即可）。鎖定後 build 全自主執行。.
debug
用 Agent 工具啟動 debugger agent，把錯誤資訊原文（含截圖/log）完整轉給它。.