HyperFrames by HeyGen
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
Interactive UI for local node modules inspection
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/antfu-node-modules-inspector)Servidores MCP que conectan la IA a servicios para el mismo trabajo
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Mismo tipo de trabajo, ordenadas como la lista de Skills
| Este node-modules-inspector | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| Autor | antfu | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| Estrellas de GitHub | 2962 | 111.265 | 67.613 | 32.407 | 29.891 |
| Último cambio de código | 17 sept 2026 | 17 nov 2026 | 13 nov 2026 | 24 jun 2026 | 30 oct 2026 |
| Licencia | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
1 skills (conjuntos de instrucciones) de antfu que la IA lee y sigue · no es un MCP server
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Claude Code
Según el README del autor y las carpetas del repo
GitHub account antfu (person), 11 years old
★ 2962 stars · code last changed 17 sept 2026
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 602140f (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
Uploading to claude.ai would fail: the description is over 200 characters (724). Use "Let the AI install it" instead
Copia esta frase y pégala en un chat de Claude Code
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Vuelve a abrir Claude Code y escribe /node-modules-inspector, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/antfu/node-modules-inspector.git /tmp/popnx-skill-antfu-node-modules-inspector-602140f && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-antfu-node-modules-inspector-602140f/skills/node-modules-inspector' ~/.claude/skills/node-modules-inspectorLa app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Coloca la carpeta node-modules-inspector en ~/.agents/skills/node-modules-inspector
~ es tu carpeta de inicio ($HOME)
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/antfu/node-modules-inspector.git /tmp/popnx-skill-antfu-node-modules-inspector-602140f && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-antfu-node-modules-inspector-602140f/skills/node-modules-inspector' ~/.agents/skills/node-modules-inspectorChecked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del IDE
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/antfu/node-modules-inspector.git /tmp/popnx-skill-antfu-node-modules-inspector-602140f && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-antfu-node-modules-inspector-602140f/skills/node-modules-inspector' ~/.agents/skills/node-modules-inspectorCopia esta frase y pégala en un chat de Cursor
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
En el chat Agent de Cursor escribe / y elige node-modules-inspector
Checked against official docs 12 nov 2026 · Source: cursor.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/antfu/node-modules-inspector.git /tmp/popnx-skill-antfu-node-modules-inspector-602140f && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-antfu-node-modules-inspector-602140f/skills/node-modules-inspector' ~/.cursor/skills/node-modules-inspectorPara otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
✓ Comandos revisados el 17 nov 2026
El texto siguiente viene del repo del autor, no de PopNx MCP
Se muestran los primeros 8000 caracteres · Abrir el archivo completo en GitHub
---
name: node-modules-inspector
description: >
Inspects a project's installed node_modules and produces three reports:
duplicated packages (installed in multiple versions), packages sorted by
install size, and maintenance actions (dep-upgrade opportunities + publint
findings, grouped by consumer/author). Use when the user wants to audit
dependencies, find duplicate packages, check what's taking up disk space in
node_modules, identify outdated peer/prod dependencies that newer dependents
could upgrade past, or list publint problems. Available as a CLI
(`npx node-modules-inspector report <duplicates|sizes|maintainers> [--json]`)
or an MCP stdio server (`npx node-modules-inspector mcp`) exposing the same
three reports as agent tools. Works with pnpm, npm, and bun.
---
# node-modules-inspector
`node-modules-inspector` is a CLI + MCP server that inspects the installed `node_modules` of the current project and produces structured reports. Three reports, same underlying analysis pipeline:
| Report | Answers |
|---|---|
| `duplicates` | Which packages are installed in multiple versions? |
| `sizes` | Which packages take up the most disk space? |
| `maintainers` | Which consumers have dep-upgrade opportunities or publint issues, grouped by package and author? |
Reports run against the real on-disk `node_modules` — no registry calls are required for the basic shape; npm metadata is fetched only to enrich the maintainers report (gated by config).
Works with pnpm, npm, and bun. The default `npx node-modules-inspector` (with no subcommand) opens a Vue web UI for humans; agents should use the `report` and `mcp` subcommands below.
## When to reach for this
Trigger on any of:
- "audit my dependencies", "find duplicate packages", "node_modules cleanup"
- "what's taking up disk space in node_modules"
- "which deps are outdated" / "what dep-upgrade opportunities are there"
- "show me publint issues across my deps"
- "who maintains my dependencies"
Don't reach for it for: registry-only questions (use `fast-npm-meta`), bundle-size analysis of a single package (use a bundler-specific tool), security audits (use `npm audit` / `osv-scanner`).
## CLI mode
All subcommands share these options:
- `--root <dir>` — project root (default: cwd)
- `--config <file>` — config file (default: `node-modules-inspector.config.{ts,js,json}`)
- `--depth <n>` — max dependency depth to traverse (default: `8`)
- `--json` — emit JSON to stdout; pretty ANSI table otherwise
Progress logs always go to stderr, so `... --json` is pipe-safe.
### duplicates
```sh
npx node-modules-inspector report duplicates --json
```
Options:
- `--min-versions <n>` — only include packages installed at this many versions or more (default: `2`)
- `--limit <n>` — cap result count
Output shape:
```json
[
{
"name": "@typescript-eslint/scope-manager",
"versions": ["8.56.1", "8.59.1", "8.59.2", "8.59.4"],
"specs": ["@typescript-eslint/scope-manager@8.56.1", "..."]
}
]
```
Versions are sorted ascending by semver. Entries are sorted by version-count descending. Use this to find dedupe targets — `pnpm dedupe` / `npm dedupe` resolves these where ranges overlap.
### sizes
```sh
npx node-modules-inspector report sizes --json --limit 20
```
Options:
- `--limit <n>` — cap result count (default: `50`)
- `--include-workspace` — include workspace packages (default: excluded; they have no meaningful install size)
Output shape:
```json
[
{
"spec": "typescript@6.0.3",
"name": "typescript",
"version": "6.0.3",
"workspace": false,
"bytes": 24346827,
"categories": {
"js": { "bytes": 15344521, "count": 200 },
"dts": { "bytes": 7002306, "count": 150 }
}
}
]
```
`categories` keys come from a fixed set: `js`, `ts`, `dts`, `json`, `bin`, `wasm`, `map`, `image`, `css`, `html`, `comp`, `doc`, `test`, `flow`, `other`. Entries are sorted by `bytes` descending.
### maintainers
```sh
npx node-modules-inspector report maintainers --json
```
Options:
- `--sort <depth|migration|latest>` — sort by consumer depth, max migration ratio, or latest release time (default: `depth`)
- `--author <handle>` — filter to consumers maintained by this author; repeatable
- `--no-publint` — exclude publint findings
- `--no-latest-only` — include consumer packages that are not on their latest major
- `--limit <n>` — cap result count
Output shape:
```json
[
{
"consumer": { "spec": "rollup-plugin-esbuild@6.2.1", "name": "rollup-plugin-esbuild", "version": "6.2.1", "depth": 1 },
"authors": [{ "type": "github", "github": "egoist", "avatar": "..." }],
"items": [
{
"kind": "dep-upgrade",
"depName": "unplugin-utils",
"depType": "prod",
"declaredRange": "^0.2.4",
"rawRange": "catalog:deps",
"catalogName": "deps",
"installedHighestVersion": "0.3.1",
"installedHighestSpec": "unplugin-utils@0.3.1",
"installedVersions": ["0.2.4", "0.3.1"],
"migratedCount": 10,
"totalCount": 11,
"migrationRatio": 0.909
},
{
"kind": "publint",
"messages": [/* publint Message objects */],
"counts": { "error": 0, "warning": 1, "suggestion": 2 }
}
],
"maxMigrationRatio": 0.909,
"latestReleasedAt": 1739000000000
}
]
```
How to read this:
- A `dep-upgrade` item means: this consumer declares `depName` at `declaredRange`, but there's a newer installed version (`installedHighestVersion`) that the range does not satisfy. `migrationRatio` is the fraction of consumers in the same cohort that already migrated — a high ratio (e.g. 0.9) means most other consumers already moved on, so this one is lagging.
- `rawRange` differs from `declaredRange` only when the consumer used a pnpm catalog reference (`catalog:deps`); `declaredRange` is the resolved range.
- A `publint` item carries the raw publint messages, partitioned by severity in `counts`.
- `authors` come from the consumer's `package.json` author/maintainers fields, with GitHub-handle detection.
Publint findings only appear when `pkg.resolved.publint` was populated. Enable that by adding `publint: true` to `node-modules-inspector.config.ts` (or by using the project's web UI which runs publint async).
## MCP mode
```sh
npx node-modules-inspector mcp
```
Starts an MCP stdio server. Exposes three tools, identical surface to the CLI:
- `nmi:report-duplicates`
- `nmi:report-sizes`
- `nmi:report-maintainers`
When configured in an MCP client (e.g. Claude Code) under server name `node-modules-inspector`, address them as `node-modules-inspector:nmi:report-duplicates`, etc.
Tool input schemas mirror the CLI options. Tool output is JSON in the exact shape shown above for each report.
Prefer MCP when:
- Multiple queries are expected in one session — the dependency tree is read once and cached across tool calls.
- The agent needs structured output schemas to drive validation.
Prefer the CLI (`report ... --json`) when shell-pipelining (`jq`, redirect, etc.) is more convenient.
## Flags the agent should know
- The first run reads `node_modules` end-to-end and caches npm metadata on disk (under `~/.node-modules-inspector` or similar). Subsequent runs are much faster.
- Workspace packages are excluded from `sizes` by default — pass `--include-workspace` if you actually want them.
- `--depth 8` is enough for almost all real projects. Increase only if the user explicitly asks about deeply-nested transitive dependencies.
- For very large monorepos, running against a single workspace package via `--root packages/<name>` is faster than the whole repo.
## Failure modes
- "No package manager detected" — the project has no `node_modules` directory, or none of pnpm/npm/bun lockfiles. Suggest the user run install first.
- Empty `duplicates` result — fine, it means everything is deduped (mention `pnpm dedupe` etc. only if user wants to verify).
- Empty `maintainers` result — usually means there are no dePregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.