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 js-static-checksgit 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/js-static-checks)<a href="https://agentmods.dev/skills/hmj1026/dhpk/js-static-checks"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/js-static-checks/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/js-static-checks"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/js-static-checks.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.00067 | $0.00754 |
| Opus 5.5 | $0.00027 | $0.00302 |
| Sonnet 5.5 | $0.00013 | $0.00151 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
js-static-checks 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.
JS static checks
Use $js-static-checks <task>; optional check, setup, and rollout actions
select the same task procedures. status remains an internal synonym for the
read-only status contract.
Resolve scope and compatibility
Identify the consumer package/frontend directory and its package.json, lock/configuration evidence first. An intentional explicit target override wins; record it separately. For version-sensitive configuration, retain exact versus range precision for ESLint and TypeScript. Missing, broad incompatible, or conflicting evidence and unspecified monorepo scope require asking and waiting before versioned reference loads or dependent changes. Runtime Node/npm versions describe the environment. Migration requires an explicit destination; group multi-version results by target. A simple directive-count check needs a scan path, not a fabricated lint version.
Select the local procedure
- Read-only status/check: read rollout's status contract
and run this skill's
scripts/status.js [--path <directory>]with Node from the consumer working directory. Omit--pathto useCLAUDE_PLUGIN_OPTION_JS_CHECK_PATH, otherwisejs/. Report deterministic JSON buckets andtotal=N strict=N nocheck=N unmarked=N. Scan immediate regular.jsfiles only;nochecktakes precedence and comment mentions do not count. Missing/unreadable/symlink paths areUNAVAILABLEwithout counts. A completed UNAVAILABLE scan can exit0; its verdict is still not PASS. - ESLint tier/configuration or shaped globals (
setup): read setup; use static checks and review patterns only as needed. - Per-leaf type-check adoption (
rollout): read rollout; use setup detail only for tier/global changes.
The local references contain all required guidance. Hook/module integration is
an optional consumer installation input, not a prerequisite or a resource
recovery path. Preserve shared tools in the consumer; this skill does not
install hooks. Missing bundled procedures/scripts are BLOCKED.
What ships with it
8 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 First seen · 64 lines · 67 tokens per session scan A 5f3f9134ecce
js-static-checks is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 754 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-10-16.
Other skills, from other repositories
typescript-testing
TypeScript testing patterns with Jest/Vitest including unit tests, integration tests, mocking strategies, and coverage. Use when writing TypeScript tests.
Unit Test Scaffold (TypeScript)
Generate TypeScript unit test skeletons (Jest/Vitest) from specifications.
ts-quality
A TypeScript quality-checking workflow that runs the TypeScript compiler, ESLint, Prettier, and tests. TypeScript is JavaScript with static type checking; ESLint checks code patterns, and Prettier checks formatting.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
validate-type-safety
Run the full 5-step TypeScript validation gate: type check, reward hacking scan, test inclusion, tests, and lint. This skill provides a structured multi-step pipeline that you cannot replicate on your own — it detects the project's package manager and linter automatically, checks tsconfig strictness, and invokes…
migrating-mastra-to-pydantic-ai
Migrate TypeScript Mastra applications to Python with Pydantic AI and, only when needed, Pydantic AI Harness. Use when source code imports @mastra/ or relies on Mastra agents, tools, workflows, memory, processors, streaming, approvals, skills, or subagents.