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 dhpk-repo-intakegit 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/dhpk-repo-intake)<a href="https://agentmods.dev/skills/hmj1026/dhpk/dhpk-repo-intake"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-repo-intake/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-repo-intake"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-repo-intake.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.00061 | $0.00665 |
| Opus 5.5 | $0.00024 | $0.00266 |
| Sonnet 5.5 | $0.00012 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
dhpk-repo-intake 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Intake
$SKILL_DIR denotes the physical directory containing the selected SKILL.md;
it is path notation, not an ambient environment variable or repository-root
lookup. Resolve it before running intake from an arbitrary consumer cwd.
When to Use
- First time onboarding a project
- Rebuilding cache after major project structural changes
- Cache expired, needs updating
When NOT to Use
- Already familiar with project structure (read cache directly)
- Only need to find specific files (use Glob/Grep)
- Day-to-day development (cache already exists)
Workflow
Docs -> Entrypoints -> Tests Map -> Next Steps
Usage
node "$SKILL_DIR/scripts/intake_cached.js" --mode auto --top 10
Cache Location
Cache stored at: ~/.claude/cache/repo-intake/<repoKey>/
| File | Description |
|---|---|
latest.md |
Latest scan results |
latest.json |
Latest scan results (JSON) |
LATEST.json |
Cache metadata |
Output
## Overview
<summary>
## Entrypoints
- {CONFIG_FILE}
- {BOOTSTRAP_FILE}
## Test Map
| Type | Pattern |
| ----------- | ----------------- |
| Unit | test/unit/ |
| Integration | test/integration/ |
| E2E | test/e2e/ |
## Next Steps
- <questions>
Verification
- Output includes Overview, Entrypoints, Test Map, Next Steps
- Entrypoints correctly identify
{CONFIG_FILE},{BOOTSTRAP_FILE} - Test Map covers Unit/Integration/E2E layers
References
references/archived/MIDWAY_HEURISTICS.md— Legacy MidwayJS heuristics (archived, for reference only)
Scripts
| Script | Purpose |
|---|---|
scripts/intake_cached.js |
Main intake with caching |
scripts/scan_repo.js |
Full repo scanner (framework-agnostic) |
scripts/scan_delta.js |
Delta scan for changed files |
Examples
Input: /dhpk:dhpk-repo-intake
Action: Execute intake script -> Output project map
What ships with it
7 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.
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 · +1 lines 4a47d068df79
- 23d ago Changed · +4 lines f8c0dc235096
- 1mo ago First seen · 102 lines · 61 tokens per session scan A 441f7f2f9e2b
dhpk-repo-intake is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 665 once invoked, about $0.0002 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-05.
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.
qshipcheck
Validates that all orchestrator Phase 2 (review), Phase 3 (acceptance), and Phase 4 (deliver) steps were executed after qship pipeline completion. Run this after qship finishes to catch any skipped steps.
harness-eval
This skill should be used when the user asks to "/harness-eval", "evaluate the build", "run QA on the app", "grade the application", "test against the spec", or wants to run the evaluator agent standalone without a full harness loop. Dispatches the harness-evaluator agent to test a running application against a…
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…
test-site
Tests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright. Use when the user wants to test, verify, or smoke-test their deployed site.
verify
Verification loop — lint -> typecheck -> unit -> integration -> e2e.