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.
curl -O https://raw.githubusercontent.com/wmt-mobile/localnest/main/.claude/skills/localnest-node-compat/SKILL.mdgit clone --depth 1 https://github.com/wmt-mobile/localnestWrote 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/wmt-mobile/localnest/localnest-node-compat)<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="Measured on agentmods" 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.00037 | $0.00365 |
| Opus 5 | $0.00018 | $0.00182 |
| Sonnet 5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
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 7d 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.
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
- Determine the exact API and version boundary first.
- Keep newer Node behavior unchanged unless the task explicitly changes it.
- 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
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.
- 7d ago First seen · 60 lines · 37 tokens per session scan A 8d8c0a44cdfe
localnest-node-compat is a skill published in the GitHub repository wmt-mobile/localnest (6 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 365 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
narsil
Use narsil-mcp code intelligence tools effectively. Use when searching code, finding symbols, analyzing call graphs, scanning for security vulnerabilities, exploring dependencies, or performing static analysis on indexed repositories.
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
materials
Create and edit materials and material instances — graph nodes, parameters, functions, custom HLSL, and instance overrides (MaterialService + MaterialNodeService). Use when the user asks to create or edit a material/material instance, wire material nodes, add material parameters, set blend/shading modes, or recreate a…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this…
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.