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/vibestackdev/vibe-stack/typescript-strictgit clone --depth 1 https://github.com/vibestackdev/vibe-stackWhat 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.00577 |
| Opus 5 | $0.00000 | $0.00289 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
typescript-strict 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strict TypeScript & Zod
Core Rules
tsconfig.jsonMUST havestrict: true- NEVER use
any— useunknownand narrow with type guards - ALWAYS provide explicit return types for Server Actions and API routes
- Prefer
interfaceovertypefor public API contracts (better error messages, extendable)
The any Ban
// ❌ NEVER
function process(data: any) { return data.name }
// ✅ Use unknown + narrowing
function process(data: unknown): string {
if (typeof data === 'object' && data !== null && 'name' in data) {
return (data as { name: string }).name
}
throw new Error('Invalid data shape')
}
// ✅ Or better — use Zod
const DataSchema = z.object({ name: z.string() })
function process(data: unknown): string {
const parsed = DataSchema.parse(data)
return parsed.name
}
Zod at Every Boundary
Validate ALL external input at these boundaries:
- Server Actions —
formDatafrom client - Route Handlers —
request.json()from external callers - Webhooks — payload from Stripe, GitHub, etc.
- URL params —
searchParamsfrom user-controlled URLs
const CreateTodoSchema = z.object({
title: z.string().min(1, 'Title is required').max(200),
priority: z.enum(['low', 'medium', 'high']).default('medium'),
dueDate: z.string().datetime().optional(),
})
type CreateTodoInput = z.infer<typeof CreateTodoSchema>
export async function createTodo(formData: FormData): Promise<ActionResponse> {
const parsed = CreateTodoSchema.safeParse({
title: formData.get('title'),
priority: formData.get('priority'),
dueDate: formData.get('dueDate'),
})
if (!parsed.success) {
return { success: false, error: parsed.error.issues[0].message }
}
// proceed with parsed.data (fully typed as CreateTodoInput)
}
Utility Types You Should Use
Partial<T>for optional updatesPick<T, 'field1' | 'field2'>for selecting fieldsOmit<T, 'id' | 'created_at'>for create inputsRecord<string, unknown>instead ofobjector{}NonNullable<T>to strip null/undefined
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.
- yesterday First seen · 73 lines · 0 tokens per session scan A c5510355c4c6
typescript-strict is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 577 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
cursor
SEO audit and implementation for Next.js, Remix, and React SPAs. Auto-attached to page, layout, and route files. Covers meta tags, Open Graph, Twitter cards, JSON-LD, sitemaps, robots.txt, i18n/hreflang, and image SEO.
diagnose
name: Issue Re-Diagnosis and Fix Template description: Template for AI to re-diagnose and fix issues that weren't resolved previously. globs.
always-on
Cursor rule "always-on" from jjcall/vibeship-boilerplate, covering core persona, how you work in this project, how you verify and validate, when you should ask for feedback or approval and how you communicate.
request
name: Issue Re-Diagnosis and Fix Template description: Template for AI to re-diagnose and fix issues that weren't resolved previously. globs.
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
react-query-tests
// ✅ CORRECT: Legacy React Query pattern const ctx = konn() .beforeEach(() => createAppRouter()) .afterEach((ctx) => ctx?.close?.()) .done().