What is analyze-bundle?

A tool for turning Next.js bundle-analyzer data into newline-separated JSON records that command-line tools can read.

Use it to review route sizes, locate large source files, inspect module dependencies, and decide which bundle changes to make.

It makes bundle reports easier to search and inspect, so you can find which routes, files, and modules contribute most to the browser download.

How vercel-labs/dev3000 configures Claude Code

About the project

vercel-labs/dev3000 is a local web debugging runtime that records a web app's server logs, browser events, errors, network activity, interactions, and screenshots in one timestamped timeline. Coding agents use it to run and inspect web applications while reproducing bugs. Its catalogue add-ons teach agents how to operate the runtime and examine its debugging evidence.

vercel-labs/dev3000 · 1,597 stars · on GitHub · dev3000.ai

Reuse

Borrowing it

Nothing to install: this file belongs to vercel-labs/dev3000. 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/vercel-labs/dev3000/main/.agents/skills/analyze-bundle/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/vercel-labs/dev3000

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/vercel-labs/dev3000/analyze-bundle/github.svg)](https://agentmods.dev/skills/vercel-labs/dev3000/analyze-bundle)

Your own site

<a href="https://agentmods.dev/skills/vercel-labs/dev3000/analyze-bundle"><img src="https://agentmods.dev/badge/skills/vercel-labs/dev3000/analyze-bundle/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/vercel-labs/dev3000/analyze-bundle"><img src="https://agentmods.dev/badge/skills/vercel-labs/dev3000/analyze-bundle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 699 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.00699
Opus 5.5	$0.00007	$0.00280
Sonnet 5.5	$0.00003	$0.00140
Haiku 4.5	$0.00002	$0.00070

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

Security

Grade A, and why

analyze-bundle 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.

.agents/skills/analyze-bundle/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

analyze-to-ndjson

Converts Next.js bundle analyzer binary .data files into grep/jq-friendly NDJSON.

Analyze artifacts

This workflow pre-generates analyzer artifacts in:

.next/diagnostics/analyze/ndjson/routes.ndjson
.next/diagnostics/analyze/ndjson/sources.ndjson
.next/diagnostics/analyze/ndjson/output_files.ndjson
.next/diagnostics/analyze/ndjson/module_edges.ndjson
.next/diagnostics/analyze/ndjson/modules.ndjson

Focus on reading these files and using their evidence to prioritize changes.

Output files

File	What's in it
`modules.ndjson`	Global module registry (`id`, `ident`, `path`)
`module_edges.ndjson`	Module dependency graph (`from`, `to`, `kind`: sync/async)
`sources.ndjson`	Per-route source tree with sizes and environment flags
`chunk_parts.ndjson`	Granular size data: one line per (source, output_file) pair
`output_files.ndjson`	Per-route output files with aggregated sizes
`routes.ndjson`	Route-level summaries

Browsing the output

Route overview

jq -s 'sort_by(-.total_compressed_size)' .next/diagnostics/analyze/ndjson/routes.ndjson

Find large sources

jq -s '
  group_by(.full_path)
  | map(max_by(.compressed_size))
  | sort_by(-.compressed_size)
  | .[0:10]
  | .[] | {full_path, compressed_size, size, route}
' .next/diagnostics/analyze/ndjson/sources.ndjson

Client-side JS

grep '"client":true' .next/diagnostics/analyze/ndjson/sources.ndjson \
  | grep '"js":true' \
  | jq -s 'sort_by(-.compressed_size) | .[0:10] | .[] | {full_path, compressed_size}'

Module dependencies

grep '"from":42,' .next/diagnostics/analyze/ndjson/module_edges.ndjson | jq .to
grep '"to":42,' .next/diagnostics/analyze/ndjson/module_edges.ndjson | jq .from
grep 'react-dom' .next/diagnostics/analyze/ndjson/modules.ndjson | jq '{id, path}'

Output files for a route

grep '"route":"/"' .next/diagnostics/analyze/ndjson/output_files.ndjson \
  | jq -s 'sort_by(-.total_compressed_size) | .[0:10] | .[] | {filename, total_compressed_size, num_parts}'

Read the full file on GitHub · 83 lines

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.

2mo ago First seen · 83 lines · 17 tokens per session scan A ec17b1a3dfe9

Subscribe to this mod's changes

analyze-bundle is a skill published in the GitHub repository vercel-labs/dev3000 (1,597 stars, last pushed 7d ago), licensed MIT. It adds 17 tokens to every session and 699 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-30.

Analytics and metrics ai devtools web

analyze-bundle next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
analyze-bundlevercel-labs/dev3000	Skill	1.6k	7d ago	MIT	A	17	Claude Code
storage-retentionget-bb/bb	Skill	4.9k	today	MIT	A	20	Claude Code, Codex
thread-listget-bb/bb	Skill	4.9k	today	MIT	A	33	Claude Code, Codex
memoryget-bb/bb	Skill	4.9k	today	MIT	A	16	Claude Code, Codex
submit-a-pluginget-bb/bb	Skill	4.9k	today	MIT	A	23	Claude Code, Codex
workflowsget-bb/bb	Skill	4.9k	today	MIT	A	21	Claude Code, Codex
provider-retryget-bb/bb	Skill	4.9k	today	MIT	A	26	Claude Code, Codex

dev3000: Skill for Claude Code