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/ts-check-status)<a href="https://agentmods.dev/commands/hmj1026/dhpk/ts-check-status"><img src="https://agentmods.dev/badge/commands/hmj1026/dhpk/ts-check-status/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/ts-check-status"><img src="https://agentmods.dev/badge/commands/hmj1026/dhpk/ts-check-status.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.00217 |
| Opus 5.5 | $0.00007 | $0.00087 |
| Sonnet 5.5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
ts-check-status 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.
What it actually says
/dhpk:ts-check-status
Forward $ARGUMENTS unchanged to the canonical
$js-static-checks status action. Pass --path <directory> to scan a
specific frontend root; when omitted, the owning Skill applies
CLAUDE_PLUGIN_OPTION_JS_CHECK_PATH or its js/ default and returns the
machine-readable directive distribution.
Not for: everyday JavaScript feature work or isolated lint-rule lookups (use js-static-checks for lint configuration).
This command is a thin Host front door. The owning Skill and its standalone
runner own classification, deterministic ordering, unavailable-path
diagnostics, and the PASS / UNAVAILABLE evidence state.
Completion: relay the Skill result without converting an unavailable scan into a passing status.
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 tokens per session aadce15f3f1a
- 23d ago Changed · -34 lines · -19 tokens per session 7cdc22a93bb6
- 1mo ago First seen · 59 lines · 37 tokens per session scan A 1aad70a24130
ts-check-status 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 217 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-09-05.
Other commands, from other repositories
typegen
Run Sanity TypeGen and troubleshoot type generation issues.
js-game-tools
Work on JavaScript or TypeScript game tooling and Firebase code.
coder
Autonomous code generation with batch file operations.
typescript-fix
Run TypeScript type-checking and resolve all errors using the typescript-expert skill.
build-fix
Fix build and TypeScript errors with minimal changes.
migrate-to-nextjs15
Upgrade this Next.js project to version 15. Update package.json dependencies to Next.js 15 and React 19. Migrate App Router patterns and update metadata API usage following latest conventions. Fix breaking changes in configuration, middleware, and API routes. Update next.config.ts with new configuration options. Test…