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 nextjsgit 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/nextjs)<a href="https://agentmods.dev/skills/hmj1026/dhpk/nextjs"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/nextjs/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/nextjs"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/nextjs.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.00075 | $0.00698 |
| Opus 5.5 | $0.00030 | $0.00279 |
| Sonnet 5.5 | $0.00015 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
nextjs 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js
Describe the framework task directly, for example: “Review build scripts in
apps/store” or “Migrate apps/store from Next.js 15.5 to Next.js 16.”
Optional review or migrate prefixes express the same tasks.
- Target. Read target-selection.md, then resolve the package/subproject and Next.js version from explicit task inputs and that package's evidence. Complete its clarification gate before reading a version resource or taking a version-dependent action. Finish this step with a read plan naming the package, requested task, compatibility target, and allowed version resource(s). Complete the plan before issuing any read that includes a version resource.
- Load. For a resolved Next.js 15.5 target, read 15.5.md.
For Next.js 16, read 16.md. Read both only for an explicit
15.5-to-16 migration or multiple resolved targets, grouping notes by target.
Execute the read plan only. For a single-target compatibility review, an
explicit override selects exactly one version resource; the installed or
manifest version is evidence, not permission to read its resource. A review
targeting 16.0.10 with a 15.5.9 manifest reads only
16.md. Source-plus-target loading requires a requested migration comparison with both roles resolved. - Apply. Match framework APIs, environment floors, build configuration, and migration traps to the selected target. Confirm the target package's React compatibility separately before any React-dependent advice. Standalone React implementation belongs to the separate React family; a Next.js task can finish from this directory without finding a peer skill.
- Verify. Report the package path, target/version evidence (including an
intentional override), selected references, recommendations or applied
changes, and actual checks. Distinguish guidance from verified runtime
behavior; report unavailable checks as
NOT_RUN.
What ships with it
5 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 · 56 lines · 75 tokens per session scan A 5c4bc5b0ae3d
nextjs is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 698 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
list-connections
Lists Power Platform connections in the current environment. Use when you need a connection ID before adding a connector to a code app.
bun-http-server
Use when building HTTP servers with Bun.serve, handling requests/responses, implementing routing, creating REST APIs, or configuring fetch handlers.
craft-content-modeling
Craft CMS 5 content modeling — sections, entry types, fields, Matrix, relations, project config, and content architecture strategy. Covers choosing section types, designing entry types and field layouts, selecting field types, configuring Matrix and nested entries, relations and eager loading, and multi-site…
outsystems-spec-driven-build
Beta Feature. This skill is a Beta Feature: a non-final OutSystems capability provided to collect customer feedback. It can change significantly, including through breaking changes, or be discontinued. The first time you use this skill in a conversation, tell the user it's a Beta Feature and share .
verify
Drive/evidence recipe for verifying wenlan changes at their real surfaces (daemon HTTP, CLI, MCP stdio). The handle file the built-in verify protocol expects; launch primitives live in the run-wenlan skill, deeper machinery (mutation audit, behavior trace, weekly sweep) in the prove skill.
python-patterns
Python backend patterns: layered architecture, async I/O, dependency injection, repository/service separation. TRIGGER when: creating routes, models, schemas, or services in a Python backend. SKIP: REST contract design (use api-design); schema/index tuning (use database-optimization). (Examples: FastAPI + SQLAlchemy +…