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/adrianomelo/cursor-project-rulesWrote 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/adrianomelo/cursor-project-rules/typescript-vscode-extension)<a href="https://agentmods.dev/rules/adrianomelo/cursor-project-rules/typescript-vscode-extension"><img src="https://agentmods.dev/badge/rules/adrianomelo/cursor-project-rules/typescript-vscode-extension/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/adrianomelo/cursor-project-rules/typescript-vscode-extension"><img src="https://agentmods.dev/badge/rules/adrianomelo/cursor-project-rules/typescript-vscode-extension.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.00000 | $0.01910 |
| Opus 5.5 | $0.00000 | $0.00764 |
| Sonnet 5.5 | $0.00000 | $0.00382 |
| Haiku 4.5 | $0.00000 | $0.00191 |
Grade A, and why
typescript-vscode-extension 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 2mo 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Project Rules Extension Development Guidelines
This document outlines best practices for developing and maintaining the Cursor Project Rules extension, which manages .mdc rule files from Git repositories to enhance AI coding assistance.
1. Extension Architecture
1.1. Project Structure
- Core Components:
cursor-project-rules/ ├── src/ │ ├── extension.ts # Entry point, registers commands │ ├── commands/ # Command implementations │ │ ├── addCursorRule.ts # UI for selecting and adding rules │ │ ├── addAllRules.ts # Adds all available rules │ │ ├── refreshRepositories.ts # Updates rule repositories │ │ ├── manageRepositories.ts # UI for repository management │ │ ├── commandA.ts │ │ ├── commandB.ts │ ├── utils/ # Utility modules │ │ ├── ruleManager.ts # Manages rule loading and installation │ │ ├── repositoryManager.ts # Handles Git repositories │ │ ├── githubApi.ts # GitHub API integration │ │ ├── cache.ts # Caching utilities │ ├── models/ # Type definitions and models │ │ ├── types.ts ├── package.json # Extension manifest ├── tsconfig.json # TypeScript configuration ├── .vscodeignore # Files to exclude from the extension package ├── README.md
1.2. Manager Classes
- RuleManager: Responsible for finding, loading, and installing
.mdcrule files. - RepositoryManager: Handles Git repository operations (clone, pull, etc.).
- Both managers should implement the singleton pattern:
export class RuleManager { private static instance: RuleManager; private constructor(private context: vscode.ExtensionContext) { this.repositoryManager = RepositoryManager.getInstance(context); } static getInstance(context: vscode.ExtensionContext): RuleManager { if (!RuleManager.instance) { RuleManager.instance = new RuleManager(context); } return RuleManager.instance; } }
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.
- 2mo ago First seen · 247 lines · 0 tokens per session scan A 3233fb695e9f
typescript-vscode-extension is a cursor rule published in the GitHub repository adrianomelo/cursor-project-rules (3 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,910 tokens. 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
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
ts
A set of TypeScript coding rules covering types, naming, file organization, error handling, and strict type checking. TypeScript is JavaScript with checks that help catch many mistakes before the program runs.
general-rule
Cursor rule "general-rule" from vinhnx/vtchat, covering development guidelines, tech stack & project overview, package management, code style and ui/ux design principles.
typescript-security
A secret scanner owns hardcoded keys. Read secrets from the environment and fail startup when a required one is missing.
naming-conventions-rule
A small set of naming rules for TypeScript, Node.js, and Next.js projects. It defines how directories and React components should be named and exported.