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/oleander/home-assistant-mcp-serverWrote 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/oleander/home-assistant-mcp-server/typescript-types)<a href="https://agentmods.dev/rules/oleander/home-assistant-mcp-server/typescript-types"><img src="https://agentmods.dev/badge/rules/oleander/home-assistant-mcp-server/typescript-types/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/oleander/home-assistant-mcp-server/typescript-types"><img src="https://agentmods.dev/badge/rules/oleander/home-assistant-mcp-server/typescript-types.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.00462 |
| Opus 5.5 | $0.00000 | $0.00185 |
| Sonnet 5.5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
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 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.
What it actually says
- File in
src/typesfolder for modularity - IMPORTANT: Namespace should match the path from
src/typesand 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
ToolsLightAttributesinsrc/tools_light_attributes.types.tsshould be renamed to:tools.light.Attributesinsrc/tools/light/attributes.types.ts
- When double or tripple, please split the name into namespaces + short type, i.e
- IMPORTANT: Do not mix logic with types. They MUST be split up between
src/types/andsrc/ - 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/typesmust match that ofsrc/(excepttypes/) - 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;
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 · 52 lines · 0 tokens per session scan A ba0baaa57cd1
typescript-types is a cursor rule published in the GitHub repository oleander/home-assistant-mcp-server (5 stars, last pushed 11mo 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.
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.