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/d-padmanabhan/agent-engineering-handbook/225-javascript-typescriptgit clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbookWhat 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.00792 |
| Opus 5 | $0.00000 | $0.00396 |
| Sonnet 5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
225-javascript-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 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JavaScript and TypeScript Engineering Gates
This rule owns mandatory policy only. Use the TypeScript and JavaScript skill (${HANDBOOK_ROOT}/skills/typescript-javascript/SKILL.md) for language patterns, configuration, testing, performance, and examples.
Shared Runtime and Supply-Chain Gates
- Pin the supported Node.js runtime and package-manager version. Use the committed lock file with immutable CI installation.
- Do not use
eval,Function, unsafe deserialization, or shell-interpreted command strings with untrusted input. - Validate external data at runtime before assigning domain types. Type declarations do not validate JSON, environment variables, messages, storage, or request bodies.
- Keep secrets out of source, browser bundles, logs, errors, command arguments, and committed configuration.
- Use ESM unless repository compatibility requires another module format; do not mix module systems accidentally.
HTTP and Server Gates
- Reuse clients or agents where the runtime supports pooling. Every outbound request requires a timeout or abort signal, status handling, bounded body processing, and runtime response validation.
- Validate URLs and constrain outbound destinations when input can influence a fetch. Do not follow redirects into untrusted networks without revalidation.
- Servers require bounded request bodies, explicit CORS policy, security headers, structured error handling, timeouts, and graceful shutdown.
- Authentication and authorization are separate. Enforce resource authorization on the server for every protected operation.
- Await or deliberately supervise every promise. Fire-and-forget work requires explicit lifecycle ownership and error reporting.
JavaScript Gates
- Production JavaScript uses
// @ts-checkand JSDoc types unless the repository documents an alternative static-analysis contract. - Exported JavaScript APIs document parameter, return, callback, generic, and shared object types with precise JSDoc.
- Do not silence type errors with broad
@ts-ignore; use a narrow@ts-expect-erroronly with a reason and a testable compatibility boundary. - Treat JSDoc assertions as compile-time aids, never as runtime validation.
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 · 62 lines · 0 tokens per session scan A c3babaef8e0d
225-javascript-typescript is a cursor rule published in the GitHub repository d-padmanabhan/agent-engineering-handbook (15 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 792 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.