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/iloveitaly/llm-ide-rules/typescriptgit clone --depth 1 https://github.com/iloveitaly/llm-ide-rulesWrote 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/iloveitaly/llm-ide-rules/typescript)<a href="https://agentmods.dev/rules/iloveitaly/llm-ide-rules/typescript"><img src="https://agentmods.dev/badge/rules/iloveitaly/llm-ide-rules/typescript.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00458 |
| Opus 5 | $0.00000 | $0.00229 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
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 3d 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
- Use
pnpmorpnpxand notnpmornpx.- Use
just js_shadcn,just pnpm, andjust js_lintinstead of executing these operations exactly. @just/javascript.just
- Use
- Node libraries are not available
- Use
lib/for generic code,utils/for project utilities,hooks/for React hooks, andhelpers/for page-specific helpers. - Prefer
function theName() {overconst theName = () => - Use
import { invariant } from @epic-web/invariantinstead of another invariant library - Use
requireEnv("VITE_THE_ENV_VAR")instead ofprocess.env.THE_ENV_VAR - Don't use
console.{log,error}. Usefrom ~/configuration/logging import logandlog.info("string", {structured: "log"})instead.
Here's how frontend code is organized in web/app/:
lib/not specific to the project. This code could be a separate package at some point.utils/project-specific code, but not specific to a particular page.helpers/page- or section-specific code that is not a component, hook, etc.hooks/react hooks.configuration/providers, library configuration, and other setup code.components/react components.ui/reusable ShadCN UI components (buttons, forms, etc.).shared/components shared across multiple pages.- create additional folders for route- or section-specific components.
Dates & Times
- Always use the ISO 8601 format when sending dates in an API request.
- Use
Temporalfor any date or time manipulation. You can assume it's available in the browser. - DateTime objects should always be converted to UTC before included in any API request. Never send a timestamp with the user's timezone.
- Unless otherwise specified, do not shift server-provided times based on the user's timezone.
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.
- 3d ago First seen · 36 lines · 458 tokens per session scan A 379d420b4144
typescript is a cursor rule published in the GitHub repository iloveitaly/llm-ide-rules (13 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 458 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
pn-aesthetics-baseline
Non-generic UI baseline for user-facing surfaces; aligns with .pncore-design.md and pn-core aesthetics reference when MCP is available.
pn-build-gate
For build/design/scaffold requests, load pn-build or pn-design; discovery and skeptic mandatory. For fix/tweak, use skills directly.
pn-godot
Godot 4.x coding conventions: GDScript typing, signal patterns, scene composition, shader style, naming, Resource patterns, multiplayer RPC safety, GDExtension registration. Use when editing .gd, .tscn, .tres, .gdshader, or project.godot files.
pn-nextjs
Next.js best practices. Data loading, server/client boundaries, streaming, mutations, and performance. For Next app/ or pages/, pn-react also applies (core React patterns); content is complementary.
pn-react
Core React conventions: function components, hooks, semantic HTML, naming, styling, performance, and component architecture. Use when editing .tsx or .jsx files. For Next.js app/ or pages/, pn-nextjs also applies.
pn-design-system
Design system rule: enforces token usage when editing CSS, SCSS, or styled components. Use tokens for color, spacing, typography; avoid one-off values. For establishing or auditing a design system, use the pn-design-system skill.