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/fmaclen/svelte-vibe-code/svelte-typescript-stylegit clone --depth 1 https://github.com/fmaclen/svelte-vibe-codeWhat 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.00245 |
| Opus 5 | $0.00000 | $0.00122 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
svelte-typescript-style 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
Svelte + TypeScript Style
- TypeScript: Project is
strict; avoidanyand unsafe casts. Prefer explicit function signatures for exported APIs. - Naming: Use descriptive names (avoid 1–2 char identifiers). Functions are verbs; variables are nouns.
- Imports: Prefer
$liband$convexaliases over deep relative paths. - UI components: Use primitives from
src/lib/components/ui. Avoid editing library components unless fixing a bug. - Formatting: Use Prettier (Svelte + Tailwind plugins). Run
npm run format. - Linting: Use
npm run lintornpm run qualitybefore committing. - Separation of concerns: Keep data fetching and mutations in Convex; keep Svelte components focused on presentation and state orchestration.
- Files: For shared logic in the app, use
.svelte.tsmodules colocated with components or under$lib.
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 · 15 lines · 0 tokens per session scan A 7a0af0827b02
svelte-typescript-style is a cursor rule published in the GitHub repository fmaclen/svelte-vibe-code (3 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 245 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
Cursor rule "vue-typescript-patterns" from soaring-xiongkulu/easyaiot, covering vue3 + typescript 开发规范, vue 组件规范, vue sfc 组件规范, typescript 规范 and 状态管理.
frontend
You are an expert in TypeScript, Node.js, Vite, Vue.js, Vue Router, Pinia, VueUse, Ant Design Vue, and UnoCSS, with a deep understanding of best practices and performance optimization techniques in these technologies.
project-overview
这是一个基于 uniapp + Vue3 + TypeScript + Vite5 + UnoCSS 的跨平台开发框架。.
vue3-typescript-auto
Vue 3 with TypeScript Standards.
svelte
When writing code for svelte (.svelte or .svelte.ts files) make sure to do the following.
nuxtjs-vue-typescript-development-rules
NuxtJS Vue TypeScript Development Rules.