typescript-extension

Coding rules for a TypeScript extension built with VS Code, Microsoft's code editor. They cover imports, separation from VS Code-specific code, tests, and formatting.

In plain words
What is it for?
Writing or reviewing TaskPlanner extension code, choosing the correct test location, using Node-style imports, and following the repository’s formatting conventions.
Why use it?
They prevent platform-specific code from spreading into the core and help keep source files and tests consistent.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/smekai/taskplanner/typescript-extension
Clone the repo
git clone --depth 1 https://github.com/smekai/taskplanner

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 174 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00174
Opus 5 $0.00000 $0.00087
Sonnet 5 $0.00000 $0.00035
Haiku 4.5 $0.00000 $0.00017

Measured 2d ago against content hash 65a5c5af36a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

typescript-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 2d 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.

.cursor/rules/typescript-extension.mdc · 16 lines

What it actually says

TypeScript conventions

  • This repo uses ESM/Node16-style imports: in .ts files, prefer relative imports that include the .js extension (e.g. import { X } from './x.js').
  • Keep src/core/** free of VS Code dependencies. Any import * as vscode from 'vscode' should live under src/extension/** (or test code that explicitly targets extension behavior).
  • Tests are split by responsibility:
    • src/test/core/**: Vitest unit tests
    • src/test/extension/**: integration tests (@vscode/test-cli)
  • Follow existing code style: single quotes, semicolons, 2-space indentation.
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.

  1. 2d ago First seen · 16 lines · 174 tokens per session scan A 65a5c5af36a0

Subscribe to this mod's changes

typescript-extension is a cursor rule published in the GitHub repository smekai/taskplanner (19 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 174 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-30.