Borrowing it
Nothing to install: this file belongs to VersoXBT/claude-initial-setup. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/VersoXBT/claude-initial-setup/main/.cursorrulesgit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWrote 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.
[](https://agentmods.dev/rules/versoxbt/claude-initial-setup/cursorrules)<a href="https://agentmods.dev/rules/versoxbt/claude-initial-setup/cursorrules"><img src="https://agentmods.dev/badge/rules/versoxbt/claude-initial-setup/cursorrules/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.
<a href="https://agentmods.dev/rules/versoxbt/claude-initial-setup/cursorrules"><img src="https://agentmods.dev/badge/rules/versoxbt/claude-initial-setup/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01329 | $0.01329 |
| Opus 5.5 | $0.00532 | $0.00532 |
| Sonnet 5.5 | $0.00266 | $0.00266 |
| Haiku 4.5 | $0.00133 | $0.00133 |
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 1mo 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.
This is a copy
95% identical to claude-initial-setup — 6 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Standards
Immutability
Always create new objects instead of mutating. Use spread operators, structuredClone, or library solutions like immer.
// WRONG
user.name = name;
items.push(newItem);
// CORRECT
const updated = { ...user, name };
const added = [...items, newItem];
const removed = items.filter(x => x.id !== id);
const mapped = items.map(x => x.id === id ? { ...x, ...changes } : x);
Python: Use @dataclass(frozen=True) and replace(). Use tuples and frozensets for immutable collections.
Go: Use value receivers and return new structs.
File Organization
- 200-400 lines per file, 800 max
- Organize by feature/domain, not by type
- Co-locate tests next to source files
- Move to
shared/only when used by 3+ features - No god files (
utils.tswith 40 exports)
Functions
- Under 50 lines each
- No nesting deeper than 4 levels
- Use early returns and guard clauses
Naming
- Variables: describe WHAT (
activeUsers), not HOW (data) - Booleans:
is/has/can/shouldprefix (isActive,hasPermission) - Functions: verb + noun (
getUserById,formatDate,validateEmail) - Collections: plural nouns (
users,orderItems) - Constants:
SCREAMING_SNAKE(MAX_RETRIES,API_BASE_URL) - Language casing: camelCase (JS/TS), snake_case (Python), PascalCase (Go exports)
Git Conventions
Commits
Format: <type>(<scope>): <description>
Types: feat, fix, refactor, docs, test, chore, perf, ci
Rules: imperative mood, lowercase, under 72 chars, no period
Branches
Format: <type>/<ticket>-<description> in kebab-case
Types: feature/, fix/, hotfix/, release/
Pull Requests
- Under 400 lines of changes
- Include summary, changes, test plan
- Squash merge for features, merge commit for releases
- Never force-push during review
Testing
TDD Workflow
- RED: Write failing test
- GREEN: Write minimal code to pass
- REFACTOR: Clean up, keep tests green
- Target 80%+ coverage
Test Structure
- Unit tests co-located:
auth.ts/auth.test.ts - Integration tests:
test/integration/ - E2E tests:
test/e2e/ - Factories for dynamic data, fixtures for static data
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.
- 1mo ago First seen · 190 lines · 1,329 tokens per session scan A a4b73332b67d
cursorrules is a cursor rule published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 5mo ago), licensed MIT. It adds 1,329 tokens to every session, about $0.0053 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to claude-initial-setup, differing in 6 lines, and is treated as a copy.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.