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.
npx agentmods add rules/oleander/home-assistant-mcp-server/typescript-typesgit clone --depth 1 https://github.com/oleander/home-assistant-mcp-serverWhat 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 | $0.00000 | $0.00462 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 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 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.
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.
- 2d 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 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.
Other cursor rules, from other repositories
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-barrel-files
Avoid barrel files and unnecessary re-exports.
vue-typescript-patterns
Cursor rule "vue-typescript-patterns" from soaring-xiongkulu/easyaiot, covering vue3 + typescript 开发规范, vue 组件规范, vue sfc 组件规范, typescript 规范 and 状态管理.
project-overview
这是一个基于 uniapp + Vue3 + TypeScript + Vite5 + UnoCSS 的跨平台开发框架。.
compose-resource-lifecycles-with-layermerge
Cursor rule "compose-resource-lifecycles-with-layermerge" from PaulJPhilp/EffectPatterns, covering compose resource lifecycles with layer.merge and example.
frontend-patterns
React/TypeScript patterns for src/ code.