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/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/vscode)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/vscode"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/vscode/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/nedcodes-ok/cursorrules-collection/vscode"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/vscode.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.00235 | $0.00235 |
| Opus 5.5 | $0.00094 | $0.00094 |
| Sonnet 5.5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
vscode 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.
What it actually says
VS Code / Cursor Rules
Workspace Setup
- Use .vscode/settings.json for project-specific settings
- Configure formatters to run on save
- Use recommended extensions list (.vscode/extensions.json)
- Set consistent editor config (indent, line endings, trim whitespace)
Debugging
- Configure launch.json for common debug scenarios
- Use compound configurations for multi-service debugging
- Set meaningful breakpoint conditions
- Use logpoints instead of console.log
Productivity
- Use multi-cursor editing for repetitive changes
- Use workspace search with file/folder filters
- Configure task runners for common build commands
- Use snippets for frequently typed patterns
Cursor AI Specific
- Place .cursorrules in project root for auto-loading
- Keep rules focused and specific to the project
- Update rules as project conventions evolve
- Use rules to enforce team standards consistently
Project Config
- Include editor config in version control
- Document required extensions in README
- Use consistent formatting across the team
- Configure file associations for custom extensions
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 · 37 lines · 235 tokens per session scan A 28e15ef3649a
vscode is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (38 stars, last pushed 7mo ago), licensed MIT. It adds 235 tokens to every session, about $0.0009 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-03.
Other cursor rules, from other repositories
16-logging
App-wide logging format and TAG conventions.
18-errors-result
Domain error models and mapping failures to UI State/Effect.
00-global
Global Android project standards — always apply.
03-android-architecture
Clean Architecture layer rules.
17-navigation
Navigation Component, Safe Args, nav animations, and nav graph conventions.
23-app-startup
Application class, SplashScreen, and AndroidX Startup.