localnest: Skill for Claude Code

.claude/skills/localnest-node-compat/SKILL.md

localnest-node-compat is a skill for Claude Code from wmt-mobile/localnest. It costs 37 tokens per session (365 once invoked), scanned A, original, MIT.

A set of guidance for making LocalNest work across different versions of Node.js, the software runtime used to run JavaScript outside a web browser. It focuses on built-in features, optional native packages, version checks, and fallback behavior.

In plain words
What is it for?
Use it when handling features such as node:sqlite, optional native dependencies, Node.js built-ins, API availability, extension loading, and checks of the published package.
Why use it?
It helps separate installation problems from runtime crashes and prevents one unsupported feature from breaking the whole product. It also keeps newer Node.js behavior unchanged where possible.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is wmt-mobile/localnest's own configuration. It tells Claude Code how to work on localnest itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything localnest configures →

Reuse

Borrowing it

Nothing to install: this file belongs to wmt-mobile/localnest. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/wmt-mobile/localnest/main/.claude/skills/localnest-node-compat/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/wmt-mobile/localnest

Made for: Claude Code.

Wrote 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.

agentmods badge for localnest-node-compat

README.md
[![agentmods](https://agentmods.dev/badge/skills/wmt-mobile/localnest/localnest-node-compat/github.svg)](https://agentmods.dev/skills/wmt-mobile/localnest/localnest-node-compat)
Your own site
<a href="https://agentmods.dev/skills/wmt-mobile/localnest/localnest-node-compat"><img src="https://agentmods.dev/badge/skills/wmt-mobile/localnest/localnest-node-compat/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.

agentmods 80×15 button for localnest-node-compat

Your own site · 80×15
<a href="https://agentmods.dev/skills/wmt-mobile/localnest/localnest-node-compat"><img src="https://agentmods.dev/badge/skills/wmt-mobile/localnest/localnest-node-compat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 365 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00365
Opus 5.5 $0.00015 $0.00146
Sonnet 5.5 $0.00007 $0.00073
Haiku 4.5 $0.00004 $0.00036

Measured 2mo ago against content hash 8d8c0a44cdfe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

localnest-node-compat 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 2mo ago.

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.

.claude/skills/localnest-node-compat/SKILL.md · 60 lines

What it actually says

LocalNest Node Compat

Use this skill for Node-version compatibility work, especially when a feature depends on:

  • node:sqlite
  • optional native packages
  • Node-specific built-ins or API availability

Quick Start

  1. Determine the exact API and version boundary first.
  2. Keep newer Node behavior unchanged unless the task explicitly changes it.
  3. Prefer capability gating and fallback over broad engine bumps when the product should still work in reduced mode.

Workflow

1. Identify the real boundary

Do not stop at package engines. Find the exact API dependency:

  • module availability
  • method availability
  • extension-loading support
  • native package install and runtime requirements

2. Separate install-time from runtime failures

Check both:

  • package install failures from native deps
  • runtime crashes from unsupported built-ins or imports

3. Gate features, not the whole product

When possible:

  • keep core MCP and search functionality working
  • disable only incompatible features
  • print a precise warning with version and action

4. Verify the published shape

Compatibility fixes are incomplete until you inspect:

  • installed package metadata
  • optional vs hard dependencies
  • global CLI behavior

Guardrails

  • Avoid static imports of version-gated modules in shared entry points.
  • Do not claim support for a Node range unless setup and startup both degrade cleanly there.
  • If optional native dependencies are used, status output must explain missing capability.

Reference

Changes

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.

  1. 2mo ago First seen · 60 lines · 37 tokens per session scan A 8d8c0a44cdfe

Subscribe to this mod's changes

localnest-node-compat is a skill published in the GitHub repository wmt-mobile/localnest (6 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 365 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-08-31.

Related

localnest-node-compat compared with skills from other repositories

localnest-node-compat next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
localnest-node-compatwmt-mobile/localnestSkill64mo agoMITA37Claude Code
narsilpostrv/narsil-mcpSkill1871mo agoApache-2.0A42Claude Code
n8n-code-toolczlonkowski/n8n-mcpSkill23kyesterdayMITA221Claude Code, Codex
n8n-subworkflowsczlonkowski/n8n-mcpSkill23kyesterdayMITA121Claude Code, Codex
sanity-singletonssanity-io/agent-toolkitSkill19710d agoMITA90Claude Code
sanity-best-practicessanity-io/agent-toolkitSkill19710d agoMITA177Claude Code
tech-specsgriddynamics/rosettaSkill370yesterdayApache-2.0A23Claude Code