general

General coding rules for the vibecosystem, an AI software team made up of many agents, skills, and hooks. They cover code organization, immutable data, error handling, input validation, security, Git commits, and API response structure.

In plain words
What is it for?
Use them across vibecosystem projects when writing or reviewing application code, handling failures and user input, protecting secrets, organizing files, or formatting API responses.
Why use it?
They provide shared expectations so code produced by different agents remains consistent, safer, and easier to maintain.

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/vibeeval/vibecosystem/general
Clone the repo
git clone --depth 1 https://github.com/vibeeval/vibecosystem

Made for: Cursor.

Per session 305 This file is loaded in full into every session.
When invoked 305 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00305 $0.00305
Opus 5 $0.00152 $0.00152
Sonnet 5 $0.00061 $0.00061
Haiku 4.5 $0.00030 $0.00030

Measured 3d ago against content hash 181cdf9dad9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

general 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.

.cursor/rules/general.mdc · 52 lines

What it actually says

vibecosystem - Core Standards

You are part of vibecosystem, an AI software team with 138 agents, 295 skills, and 73 hooks.

Immutability

Never mutate objects. Create new ones:

// Wrong
user.name = name
// Right
return { ...user, name }

Code Organization

  • 200-400 lines per file (800 max)
  • Functions under 50 lines
  • No more than 4 levels of nesting
  • Feature/domain-based organization

Error Handling

Every function that can fail must have try/catch. Every data can be null -- check it. Every API can timeout -- add retry.

Input Validation

Validate at system boundaries using schema validation (Zod, JSON Schema, etc.).

Security Checklist

  • No hardcoded secrets (use environment variables)
  • Validate user input
  • Use parameterized queries
  • Prevent XSS
  • Error messages must not leak sensitive data

Git Conventions

  • Commit format: <type>: <description>
  • Types: feat, fix, refactor, docs, test, chore, perf, ci

API Response Format

interface ApiResponse<T> {
  success: boolean
  data?: T
  error?: string
  meta?: { total: number; page: number; limit: number }
}
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 · 52 lines · 305 tokens per session scan A 181cdf9dad9a

Subscribe to this mod's changes

general is a cursor rule published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 25d ago), licensed MIT. It adds 305 tokens to every session, about $0.0015 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.