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 skills add hmj1026/dhpk --skill repo-verifygit 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/skills/hmj1026/dhpk/repo-verify)<a href="https://agentmods.dev/skills/hmj1026/dhpk/repo-verify"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/repo-verify/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/repo-verify"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/repo-verify.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.00667 |
| Opus 5.5 | $0.00026 | $0.00267 |
| Sonnet 5.5 | $0.00013 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
repo-verify 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 yesterday.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Verify
Workflow
Run read-only in the consumer repository. Normalize no mode or full to full
stages and fast to lint + unit; accept only fast or full. Attach
--integration <path> and --e2e <path> only to their matching stages.
Use a project-installed
.claude/dhpk/skills/repo-verify/scripts/verify-runner.js when present. If it
is absent, use the package-local $SKILL_DIR/scripts/verify-runner.js for a
Node project. $SKILL_DIR is the installed directory containing this
SKILL.md; its adjacent scripts/lib/runner-utils.js is part of the same
local closure, and the consumer cwd remains unchanged. A runner's crash,
missing overall verdict, execution error, or explicit semantic FAIL is
terminal and does not fall through. A Markdown FAIL or summary.json
overallPass=false remains failure even when the runner exits zero. When no
applicable runner is available, use the non-Node/manifest fallback and stage rules in
references/workflow.md; unsupported manifests are
terminal failures.
When NOT to Use
- A check should edit, format, build, or fix the repository.
- Dependency security review is the goal (use
$change-verdict deps). - Merge approval or code-review verdict is the goal.
Output
For a runner, prefix output with Source: runner and preserve its summary.
For fallback, report Source: fallback, every lint/typecheck/unit/
integration/e2e stage as PASS, FAIL, or SKIP with command/reason, and an
agreeing overall verdict. Invalid modes, unsupported manifests, runner
failures, and execution errors are terminal FAIL/BLOCKED results.
Verification
- Mode and optional paths were normalized before execution.
- Runner precedence and terminal failure boundary were respected.
- Every applicable stage has a result and exact command or skip reason.
- Semantic overall verdict agrees with the stage results and source is named, regardless of CLI exit status.
References
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 188 B
- distribution.yaml 3.2 KB
- references/dhpk-feature-verify/agents/openai.yaml 262 B
- references/dhpk-feature-verify/distribution.yaml 817 B
- references/dhpk-feature-verify/references/blackbox-testing.md 9.0 KB
- references/dhpk-feature-verify/references/environments.md 5.2 KB
- references/dhpk-feature-verify/references/output-template.md 5.1 KB
- references/dhpk-feature-verify/references/safety-rules.md 2.9 KB
- references/dhpk-feature-verify/references/verification-playbook.md 3.0 KB
- references/dhpk-feature-verify/scripts/api-exec.sh 972 B runs code
- references/dhpk-feature-verify/scripts/health-probe.sh 475 B runs code
- references/dhpk-feature-verify/SKILL.md 6.5 KB
- references/workflow.md 2.8 KB
- scripts/lib/runner-utils.js 8.4 KB runs code
- scripts/verify-runner.js 9.6 KB runs code
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.
- yesterday Changed · +8 lines 7b4c604c665b
- 23d ago First seen · 56 lines · 64 tokens per session scan A f9a27268fdac
repo-verify is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 667 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-24.
Other skills, from other repositories
verify
A four-layer check for deciding whether a software feature is truly finished: code checks, runtime tests, end-to-end tests, and user-reported confirmation.
validation-sample
A skill for building a reference test set of 50–100 realistic scenarios for checking an agent or product. It separates user inputs from expected answers to prevent answer leakage and requires at least 90% before shipping.
opsx:tdd
Adds a TDD gate to OpenSpec — write REAL failing tests from specs//.md before implementation. Run after opsx:propose and before opsx:apply. Solid RED — never expect.fail placeholders.
evaluator-write-qa-parallel
Internal Auto-Harness evaluator skill for parallel sprint QA and QA report writing. Use only inside the Evaluator subagent during evaluatorqaparallel.
evaluator-write-qa
Internal Auto-Harness evaluator skill for sprint QA and QA report writing. Use only inside the Evaluator subagent during qa mode.
evaluator-write-retest-parallel
Internal Auto-Harness evaluator skill for parallel sprint retest and retest report writing. Use only inside the Evaluator subagent during evaluatorretestparallel.