bundle-analysis

bundle-analysis is a skill for Claude Code, Codex from sybil-solutions/local-studio. It costs 28 tokens per session (301 once invoked), scanned A, a copy of bundle-analysis, MIT.

A bundle-size analysis workflow for measuring a web or software package's compiled output, comparing it with another version, and inspecting what it contains.

In plain words
What is it for?
Use it to compare a bundle with a base revision, inspect its largest modules and dependencies, measure current size, and clean up retained comparison files.
Why use it?
It provides repeatable checks for size changes and helps distinguish real size differences from temporary comparison data or misleading readable summaries.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to compare a bundle with a base revision, inspect its largest modules and dependencies, measure current size, and clean up retained comparison files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sybil-solutions/local-studio/bundle-analysis
About the project

Local Studio is a local-first control panel for running, managing, and using self-hosted large language model backends such as vLLM, SGLang, llama.cpp, and ExLlama. It lets users launch models, monitor GPU and runtime state, chat through OpenAI-compatible endpoints, and run agent sessions from a desktop or connected mobile device. The catalogue skills and instruction support agent workflows with Local Studio and its controllers.

sybil-solutions/local-studio · 1,828 stars · on GitHub · localstudio.ai

Install

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.

Any agent
npx skills add sybil-solutions/local-studio --skill bundle-analysis
Clone the repo
git clone --depth 1 https://github.com/sybil-solutions/local-studio

Made for: Claude Code, Codex.

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 bundle-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/sybil-solutions/local-studio/bundle-analysis/github.svg)](https://agentmods.dev/skills/sybil-solutions/local-studio/bundle-analysis)
Your own site
<a href="https://agentmods.dev/skills/sybil-solutions/local-studio/bundle-analysis"><img src="https://agentmods.dev/badge/skills/sybil-solutions/local-studio/bundle-analysis/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 bundle-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/sybil-solutions/local-studio/bundle-analysis"><img src="https://agentmods.dev/badge/skills/sybil-solutions/local-studio/bundle-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 301 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 100% copy Near-identical to another mod 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.00028 $0.00301
Opus 5.5 $0.00011 $0.00120
Sonnet 5.5 $0.00006 $0.00060
Haiku 4.5 $0.00003 $0.00030

Measured 3d ago against content hash 94ab06b3b070, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bundle-analysis 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 3d 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.

Origin

This is a copy

100% identical to bundle-analysis — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.repos/effect-smol/.agents/skills/bundle-analysis/SKILL.md · 26 lines

What it actually says

Read packages/tools/bundle/README.md, then select one workflow:

  • Stable comparison: pnpm bundle-compare <base-ref>. Use HEAD~1 for the latest commit. Read tmp/bundle-stats.txt and report non-zero differences.
  • Selected comparison: pnpm bundle-compare-selected --base <ref> scratchpad/<fixture>.ts. Use only user-named or investigation-local fixtures; keep temporary fixtures out of the stable corpus.
  • Composition: pnpm bundle-analyze scratchpad/<fixture>.ts. Read raw data first and report the largest modules, dependency groups, and surprising inclusions. Its readable-name output is not an exact size measurement.
  • Current size: Build immediately before the direct bundle report so Effect packages resolve from current dist output.
  • Cleanup: Stable comparisons retain tmp/bundle-base for reuse unless cleanup is requested. Remove selected-comparison state retained with --keep-base after its final use. Verify cleanup without disturbing unrelated worktrees.

The task is complete when the selected artifact is inspected, requested size or composition findings are reported, generated paths are named, and comparison state follows the selected workflow's retention policy.

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. 3d ago First seen · 26 lines · 28 tokens per session scan A 94ab06b3b070

Subscribe to this mod's changes

bundle-analysis is a skill published in the GitHub repository sybil-solutions/local-studio (1,828 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 301 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to bundle-analysis, differing in 0 lines, and is treated as a copy.