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.
git clone --depth 1 https://github.com/vinhnx/vtchatWrote 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/vinhnx/vtchat/general-rule)<a href="https://agentmods.dev/rules/vinhnx/vtchat/general-rule"><img src="https://agentmods.dev/badge/rules/vinhnx/vtchat/general-rule/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/vinhnx/vtchat/general-rule"><img src="https://agentmods.dev/badge/rules/vinhnx/vtchat/general-rule.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.02939 | $0.02939 |
| Opus 5.5 | $0.01176 | $0.01176 |
| Sonnet 5.5 | $0.00588 | $0.00588 |
| Haiku 4.5 | $0.00294 | $0.00294 |
Grade A, and why
general-rule 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 today.
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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Guidelines
Tech Stack & Project Overview
- Monorepo: Turborepo-managed, with
apps/(main: Next.js web app) andpackages/(shared code:common,shared,ai,ui, etc.). - Core Technologies: Next.js 15 (App Router), React 19.0.0, TypeScript, Tailwind CSS, shadcn/ui, Zustand, Drizzle ORM (Neon PostgreSQL), Better-Auth, Framer Motion, Lucide icons.
- AI/Agents: Agentic Graph System in
packages/ai/(supports OpenAI, Anthropic, Google, Groq, etc.). - Best Practices: Use environment variables, enums for string keys, named exports, shadcn/ui for UI, Bun for all scripts, and document changes in
memory-bank/.
Package Management
- Use
buninstead ofnpmfor all operations
Code Style
- Make sure no string in #codebase, use enum pattern.
- Don't hard code values in the codebase.
- Use environment variables for configuration (e.g., API keys, product IDs, ADMIN_USER_IDS for Better-Auth admin access - supports comma-separated user IDs)
- Use centralize enum for custom reusable keys.
- 4-space indentation, single quotes, 100 char line length
- PascalCase components, camelCase hooks/utils, kebab-case files
- Named exports preferred over default exports
- Use oxlint for fast comprehensive linting (run
bun run lint) - Use Prettier for markdown files only (run
bun run format)
UI/UX Design Principles
- Minimal Design: Follow shadcn/ui principles with clean, minimal aesthetics
- No Colors: Use only black/white/muted colors (avoid gradients, bright colors)
- Minimal Icons: Reduce icon usage to essentials only
- Clean Typography: Rely on typography hierarchy over visual decorations
- Neutral Palette: Use
text-muted-foreground,bg-muted, standard shadcn colors - Simple Interactions: Avoid flashy animations or complex visual effects
Development Workflow
- Make sure you DO NOT CREATE ANY debug and test FILES IN ./ ROOT DIRECTORY. Only use files in /temps or apps/web/app/tests/ or /scripts.
- Make sure you run
bun devand check the app console to see if there are any errors before starting to work on anothers task. fix it first. - Plan first, then implement. For substantial changes, request maintainer feedback on the plan before coding.
- REQUIRED: Run
bun run biome:formatto auto-fix formatting issues - NEVER commit changes yourself - DO NOT execute
git commitunless you have my approval - Run
bun run lint(oxlint) for comprehensive error checking - Run
bun run buildto verify compilation before major changes - Test core functionality after significant 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.
- today First seen · 300 lines · 2,939 tokens per session scan A e7225c7e478c
general-rule is a cursor rule published in the GitHub repository vinhnx/vtchat (59 stars, last pushed 1mo ago), licensed MIT. It adds 2,939 tokens to every session, about $0.0118 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-10-15.
Other cursor rules, from other repositories
agent-development
Python agents are typically in folders named agent-py/ or agent/ and use the sdk-python/ package.
update-ai-sdk
Update ai-sdk(ai, @ai/) to latest.
nestjs-best-practices
../../.claude/rules/nestjs-best-practices.md.
all-ts
../../.claude/rules/all-ts.md.
project-core
Repository-wide project instructions. Canonical rules are in AGENTS.md.
components
React component, styling, theme, accessibility, and RTL instructions.