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.
npx agentmods add rules/kk5190/viberepo/cursorrulesgit clone --depth 1 https://github.com/kk5190/viberepoWhat 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 | $0.00371 | $0.00371 |
| Opus 5 | $0.00186 | $0.00186 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
cursorrules 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 2d 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.
What it actually says
Project Rules for viberepo
Generated by VibeRepo — https://github.com/user/viberepo
Stack: Node.js | Language: typescript | ORM: none
Project Context
You are working on "viberepo", a Node.js application. Always read PROJECT_MAP.md first to understand the full project structure. Always read llms.txt for a quick overview of the codebase.
Architecture Rules
- Follow the existing file structure and naming conventions.
- Keep files focused and single-responsibility.
- Do NOT create files outside the established directory structure without asking.
- When creating new features, follow the patterns established in existing code.
General Rules
- Follow the conventions established in the existing codebase.
- Prefer clarity over cleverness.
Code Quality
- Write strict TypeScript — never use
any. Useunknownwith type guards instead. - Handle all error cases explicitly. Never swallow errors silently.
- Write pure functions when possible. Minimize side effects.
- Add JSDoc comments for all public functions and complex logic.
- Keep functions small (<30 lines). Extract when complexity grows.
Testing
- Every new feature must include tests.
- Test behavior, not implementation details.
- Use descriptive test names: "should [expected behavior] when [condition]".
Git Discipline
- Make atomic commits — one logical change per commit.
- Use conventional commits: feat:, fix:, refactor:, docs:, test:, chore:.
- Never commit console.log, debugger, or TODO without a tracking issue.
Context Management
- Do NOT read node_modules, dist, build, .next, or coverage directories.
- Reference docs/ai-context/ for architecture and conventions.
- After making structural changes, remind the user to run
viberepo sync.
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.
- 2d ago First seen · 47 lines · 371 tokens per session scan A abf97e1b2473
cursorrules is a cursor rule published in the GitHub repository kk5190/viberepo (2 stars, last pushed 5mo ago), licensed MIT. It adds 371 tokens to every session, about $0.0019 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.