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/blockmatic/basilicWrote 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/blockmatic/basilic/typescript)<a href="https://agentmods.dev/rules/blockmatic/basilic/typescript"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/typescript/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/blockmatic/basilic/typescript"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/typescript.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.00483 |
| Opus 5.5 | $0.00000 | $0.00193 |
| Sonnet 5.5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
typescript 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 1mo 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
- TypeScript strict mode
- Never use
any - Use ts-reset (
@total-typescript/ts-reset) no-unsafe-*disabled- ESM with bundler/Node resolution
- Never use CommonJS (
__dirname,__filename,require,module.exports) - ESM:
fileURLToPath(import.meta.url)with descriptive names (scriptDir, not__dirname) - Monorepo with
@repo/*subpath exports - Subpath exports (
@repo/utils/async) - Named exports (exception: Next.js pages/layouts)
- Type-only (
import type) - Interfaces for object shapes
- Types for unions/utilities/mapped/Zod inference
- Avoid enums (use const objects/union types)
- Infer types when possible (
type User = z.infer<typeof userSchema>) - Always camelCase variables
- Booleans with aux verbs (
isLoading,hasError) - Lowercase-with-dashes directories
- RORO (
({ name }: Input) => ({ id, name })) - Functional (avoid classes/decorators)
- Use
functionkeyword for named function definitions, arrow functions for inline functions and React component methods - Fail-fast: Early returns (guard clauses), avoid else after return/throw; keep success path at top indentation
- Single-line (
if (!value) return null); no braces for single-statement blocks (curly multi) - Nesting: Prefer max 3–4 levels; extract helpers or invert conditions to flatten
- Explicit return types for exported functions/API handlers
- Zod-first (validate at boundaries)
- Colocate schemas (
app/api/users/schema.ts) - Validation functions return results (never throw)
- Avoid unnecessary runtime validations in functions, we validate at build time
- Prefer inline expressions, minimize code without sacrificing readability
- No intermediate vars unless reused (
process(fetch())notconst data = fetch(); process(data)). Exceptions: destructuring, readability, error handling - Avoid thin wrappers: don't export functions that only delegate to another without adding logic; inline at call sites or consolidate
- Lodash per-function (
import isEmpty from "lodash-es/isEmpty")
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.
- 1mo ago Changed · +1 lines · -473 tokens per session d7fc3b435938
- 1mo ago First seen · 40 lines · 473 tokens per session scan A 88ae9f8aaa51
typescript is a cursor rule published in the GitHub repository blockmatic/basilic (90 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 483 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-30.
Other cursor rules, from other repositories
hatch3r-typescript-patterns
TypeScript and JavaScript typing mechanics — satisfies over as, discriminated unions, branded types, strict utility types, barrel exports, and import ordering.
typescript-coding-standards
Production TypeScript coding standards.
testing-standards-typescript
When writing tests for typescript.
typescript-error-handling
Error handling patterns for TypeScript with Sentry.
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.
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.