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 agentmods add skills/denoland/deno/node-compatnpx skills add denoland/deno --skill node-compatgit clone --depth 1 https://github.com/denoland/denoWhat 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 | $0.00037 | $0.01264 |
| Opus 5 | $0.00018 | $0.00632 |
| Sonnet 5 | $0.00007 | $0.00253 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade A, and why
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 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node Compat Test
Work on Node.js compatibility test $ARGUMENTS.
Step 1: Build and run the test
./x build
./x test-compat $ARGUMENTS
If the test passes, report success and ensure test is specified in
tests/node_compat/config.jsonc.
Step 2: Diagnose the failure
Read the test file to understand what it tests:
# Tests live under tests/node_compat/test/
Use Grep and Read to find the test source, then analyze:
- What Node.js API or behavior is being tested?
- What is the actual error or assertion failure?
- Where is the relevant Deno implementation? Check
ext/node/(polyfills, ops, internal bindings),runtime/, orcli/.
Read the corresponding Node.js docs and/or source code to understand the expected behavior.
Step 3: Classify the failure
Determine which category this failure falls into:
A. Fixable bug
The Deno implementation is wrong or incomplete, but can be corrected. This includes:
- Missing method/property on a polyfill
- Wrong return value or error type
- Missing event emission
- Incorrect argument handling
- Hard-to-fix but still fundamentally implementable behaviors
Action: Fix the implementation (Step 4).
B. Inherent incompatibility
The test relies on Node.js internals or architecture that Deno fundamentally cannot or will not support:
internalBinding()calls to Node's C++ layer- Node.js-specific CLI flags (
--inspect,--prof, etc.) - V8 internals exposed through Node-specific APIs
- Node.js-specific build/addon tooling (node-gyp internals)
- Tests for Node.js's own test infrastructure
Action: Ignore the test with a reason (Step 5).
C. Not worth fixing
The test exercises an edge case or behavior that is technically possible but provides negligible value:
- Extremely obscure error message wording differences
- Node.js-specific deprecation warnings
- Behavior that no real-world code depends on
Action: Ignore or skip the test with a reason (Step 5).
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 · 188 lines · 37 tokens per session scan A 49498c75721c
node-compat is a skill published in the GitHub repository denoland/deno (108,342 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 1,264 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-30.
Other skills, from other repositories
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
angular-developer
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component…
reference-core
Explains the mental model and architecture of the code under packages/core. You MUST use this skill any time you plan to work with code in packages/core.
migrate-oxfmt
Guide for migrating a project from Prettier or Biome to Oxfmt. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's formatter from Prettier or Biome to Oxfmt.
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
insta-snapshots
Guide for working with and updating insta snapshot tests in Oxc without terminal interaction.