typescript-types

A set of TypeScript rules for organizing type definitions separately from application code. It uses folder paths and namespaces to group related types and encourages reusable built-in type tools.

In plain words
What is it for?
Use it when adding or renaming TypeScript types, especially nested types such as tool attributes. It also specifies how to check the result with the project's lint command.
Why use it?
It keeps type files consistent with the source code, making large projects easier to navigate and reducing confusion between data definitions and program logic.

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/oleander/home-assistant-mcp-server/typescript-types
Clone the repo
git clone --depth 1 https://github.com/oleander/home-assistant-mcp-server

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 462 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.00462
Opus 5 $0.00000 $0.00231
Sonnet 5 $0.00000 $0.00092
Haiku 4.5 $0.00000 $0.00046

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

Security

Grade A, and why

typescript-types 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-types.mdc · 52 lines

What it actually says

  • File in src/types folder for modularity
  • IMPORTANT: Namespace should match the path from src/types and the type the name of the file
  • Prefer single word type names over double
    • When double or tripple, please split the name into namespaces + short type, i.e
      • ToolsLightAttributes in src/tools_light_attributes.types.ts should be renamed to:
      • tools.light.Attributes in src/tools/light/attributes.types.ts
  • IMPORTANT: Do not mix logic with types. They MUST be split up between src/types/ and src/
  • Namespace tools encapsulates tool-related types
  • Nested namespace light groups types specific to light tools
  • Attributes interface defines properties (e.g. brightness, color, isOn)
  • Incorporates advanced TypeScript features:
    • Intersection, union, mapped, and conditional types
    • Utility types like Partial, Required, Record, Pick, and Omit
  • Export declarations ensure types are accessible application-wide
  • Types can be imported to enhance type safety and maintainability
  • Verify types using bun run lint --fix
  • The file structure in src/types must match that of src/ (except types/)
  • Changes should be done to the source types, not the type files (such as renaming types or classes)
  • In other words; the source code adapts to the types
  • The namespace + type should match the pathname

Example

// src/types/tools/light.ts
namespace tools {
  export namespace light {
    export interface Attributes {
      brightness: number;
      color: string;
      isOn?: boolean;
      mode?: Mode;
      customAttributes?: Record<string, string | number>;
    }
    
    export type Mode = "ambient" | "spotlight" | "flash";
    
    export type AdvancedAttributes = Attributes & {
      transitionDuration: number;
    };
    
    export type CheckBrightness<T> = T extends { brightness: number } ? "Valid" : "Invalid";
  }
}

export = tools;
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 · 52 lines · 0 tokens per session scan A ba0baaa57cd1

Subscribe to this mod's changes

typescript-types is a cursor rule published in the GitHub repository oleander/home-assistant-mcp-server (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 462 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.