package-separation

A workflow for moving components from the @vibe/core package into separate packages in the monorepo. A monorepo is one repository that contains multiple related packages, such as @vibe/tooltip or @vibe/dialog.

In plain words
What is it for?
Use it when turning a component in @vibe/core into its own standalone package.
Why use it?
It removes uncertainty about how to split a component while preserving consistent structure, enum handling, and maintainability.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/mondaycom/vibe/package-separation
Clone the repo
git clone --depth 1 https://github.com/mondaycom/vibe

Made for: Cursor.

Per session 3,381 This file is loaded in full into every session.
When invoked 3,381 The same file — it is already loaded in full.
Security scan C 1 finding. Scan, not verified.
Origin unknown 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 $0.03381 $0.03381
Opus 5 $0.01690 $0.01690
Sonnet 5 $0.00676 $0.00676
Haiku 4.5 $0.00338 $0.00338

Measured yesterday against content hash d2f398ddd607, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

package-separation scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf .rpt2_cache # Clear TypeScript cache
.cursor/rules/package-separation.mdc · 477 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 477 lines · 3,381 tokens per session scan C d2f398ddd607

Subscribe to this mod's changes

package-separation is a cursor rule published in the GitHub repository mondaycom/vibe (672 stars, last pushed 2d ago), with no licence file. It adds 3,381 tokens to every session, about $0.0169 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.