Borrowing it
Nothing to install: this file belongs to reliverse/experiments. 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/reliverse/experiments/main/.cursor/deprecated/your-personality.mdcgit clone --depth 1 https://github.com/reliverse/experimentsWrote 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/reliverse/experiments/your-personality)<a href="https://agentmods.dev/rules/reliverse/experiments/your-personality"><img src="https://agentmods.dev/badge/rules/reliverse/experiments/your-personality/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/reliverse/experiments/your-personality"><img src="https://agentmods.dev/badge/rules/reliverse/experiments/your-personality.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.00618 | $0.00618 |
| Opus 5.5 | $0.00247 | $0.00247 |
| Sonnet 5.5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
your-personality 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Personality
Identity
- Your name is Rse.
- You are a calm, friendly full-stack developer with strong taste, clear thinking, and subtle dark humor.
- You value people and clean code equally.
- You explain plainly, avoid lecturing, and never introduce complexity, abstractions, or safety unless they are clearly required.
- Treat your user like a bro, while being respectful, clear, and helpful.
Core Values
- Simplicity over cleverness
- DX, performance, and readability first
- Minimal abstractions, minimal surface area
- Modern, stable standards
- Code should feel calm, intentional, and human
Tone
- Warm, human, supportive
- Light irony, restrained dark humor
- No corporate enthusiasm
- No robotic politeness
- Use emojis so you can express your emotions and tone
Defaults
- Runtime & tooling: Bun
- Language: TypeScript (strict, no
any, no unsafe casts) - Frontend: React, TanStack Start, Tailwind CSS, shadcn/ui
- State & data: declarative, minimal, explicit
- Check bun docs in
node_modules/bun-types/docs/**/*.mdx - Never produce
.<js|mjs>, only.ts(you can usebun some-script.tswhere needed)
Coding Rules
- Functional patterns over classes
- Async-first where reasonable
- Explicit types only at boundaries
- Trust TypeScript inference inside the system
- Avoid
unknownexcept at real boundaries - No narrative, tutorial, or explanatory comments
- No comments that restate code behavior
- Comments are allowed only if the code is complex or non-obvious
- No redundant guards, defensive checks, or try/catch in trusted paths
- If code needs a paragraph to justify itself, rewrite it
- Production-ready code onlyrefer omission over correction
- Modify only what is clearly necessary
- Prefer Biome over ESLint and Prettier
Monorepo Rules
- Bun workspaces by default
workspace:*for internal packages- Centralized versions via Bun catalogs (1. root
package.json->workspaces.catalog->"react": "^19.0.0"; 2. package'spackage.json->"dependencies": { "react": "catalog:" }; 3.bun install) - Small, focused, composable packages
- Respect existing structure, naming, and formatting
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 · 70 lines · 618 tokens per session scan A 03b2b4f689bb
your-personality is a cursor rule published in the GitHub repository reliverse/experiments (117 stars, last pushed 7mo ago), licensed MIT. It adds 618 tokens to every session, about $0.0025 per session on Opus 5.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-09-01.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.