vibeyard: Skill for Claude Code

.claude/skills/add-npm-dependency/SKILL.md

add-npm-dependency is a skill for Claude Code from elirantutia/vibeyard. It costs 100 tokens per session (1,496 once invoked), scanned A, original, MIT.

A project-specific guide for adding npm packages, which are reusable JavaScript libraries, to an Electron application. It explains how to install the latest version and account for the app's main, preload, and renderer builds.

In plain words
What is it for?
Use it when adding or upgrading an npm dependency, including choosing its build target, updating package files, and following the project's Node and npm conventions.
Why use it?
It helps avoid bundling, CSS, native-module, and lockfile problems caused by installing a dependency the wrong way.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md.

This is elirantutia/vibeyard's own configuration. It tells Claude Code how to work on vibeyard itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vibeyard configures →

About the project

Vibeyard is an IDE and project workspace for managing multiple AI coding-agent sessions, including parallel runs, split panes, task boards, cost tracking, and session resumption. It is for developers who use Claude Code, Codex CLI, or Gemini CLI and need to organize many agent-driven coding tasks. The catalogue add-ons provide commands, skills, and instructions for working with Vibeyard.

elirantutia/vibeyard · 1,369 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to elirantutia/vibeyard. 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/elirantutia/vibeyard/main/.claude/skills/add-npm-dependency/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/elirantutia/vibeyard

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.

agentmods badge for add-npm-dependency

README.md
[![agentmods](https://agentmods.dev/badge/skills/elirantutia/vibeyard/add-npm-dependency/github.svg)](https://agentmods.dev/skills/elirantutia/vibeyard/add-npm-dependency)
Your own site
<a href="https://agentmods.dev/skills/elirantutia/vibeyard/add-npm-dependency"><img src="https://agentmods.dev/badge/skills/elirantutia/vibeyard/add-npm-dependency/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 add-npm-dependency

Your own site · 80×15
<a href="https://agentmods.dev/skills/elirantutia/vibeyard/add-npm-dependency"><img src="https://agentmods.dev/badge/skills/elirantutia/vibeyard/add-npm-dependency.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,496 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00100 $0.01496
Opus 5 $0.00050 $0.00748
Sonnet 5 $0.00020 $0.00299
Haiku 4.5 $0.00010 $0.00150

Measured 11d ago against content hash c8994a57ab38, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

add-npm-dependency 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 11d 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.

.claude/skills/add-npm-dependency/SKILL.md · 94 lines

How it starts

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

Adding an npm Library

This is an Electron app with three separate build targets (main, preload, renderer) and a few non-obvious bundling rules. Adding a dependency the wrong way silently breaks CSS, native modules, or the renderer bundle. Follow this guide every time.

Golden Rule: install the latest, caret-pinned

Always install the newest published version. Never hand-edit package.json to set or downgrade a version.

npm install <pkg>@latest          # runtime dependency
npm install -D <pkg>@latest       # dev / build-only tool (types, bundlers, test libs)
  • This records a caret range ^x.y.z — the repo convention (every dep in package.json uses ^). Leave it as a caret range.
  • package-lock.json is committed and gets updated by the install. Both package.json and package-lock.json are part of your change — stage both.
  • Use npm only (the lockfile is package-lock.json — not yarn, not pnpm).
  • Node v24 is pinned in .nvmrc; engines.node is >=18. Run nvm use first if needed.

Step 1 — Decide which build target consumes the package

This determines every gotcha that follows.

Target Source dirs How it's built What's allowed
Renderer src/renderer/** Bundled by esbuild into one IIFE (build:renderer) Plain JS/TS deps only. No Node built-ins, no native modules.
Main src/main/**, src/shared/** tsc → CommonJS (dist/main/) Any Node dep, including native modules. Resolved via require at runtime against node_modulesnot bundled.
Preload src/preload/**, src/shared/** tsc → CommonJS (dist/preload/) Runs in Node/Electron context; same rules as main.
  • A pure JS/TS library used in the UI (like marked, dompurify, gridstack, @xterm/*) just gets imported in renderer code and esbuild bundles it. Nothing else to do (except CSS — see Step 2).
  • A library that touches the filesystem, spawns processes, or has a .node binary belongs in main/preload only.

Read the full file on GitHub · 94 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.

  1. 11d ago First seen · 94 lines · 100 tokens per session scan A c8994a57ab38

Subscribe to this mod's changes

add-npm-dependency is a skill published in the GitHub repository elirantutia/vibeyard (1,369 stars, last pushed 8d ago), licensed MIT. It adds 100 tokens to every session and 1,496 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

printing-press-import

Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…

mvanhorn/cli-printing-press · 104 tokens

work

Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.

automagik-dev/genie · 26 tokens

trace

Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for fix handoff.

automagik-dev/genie · 25 tokens

preview-design

Render a real artifact through this branch's local MERIDIAN design code (not the published npm package) so the team can test the new Design Convention on the document / handoff / platform surfaces before it ships. Use for /preview-design, "preview the design convention", "render this with the new design", or Design…

egregore-labs/egregore · 71 tokens

sw-do

Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".

anton-abyzov/specweave · 41 tokens

done

Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".

anton-abyzov/specweave · 0 tokens