mskills typescript.instructions.md

A set of TypeScript project instructions covering modules, type safety, Node.js APIs, and error handling. TypeScript is JavaScript with features that describe the kinds of values code may use.

In plain words
What is it for?
Use it when writing or reviewing TypeScript in the project, especially imports, strict typing, file-system code, and caught errors.
Why use it?
It gives coding agents the project-specific rules needed to produce consistent and safer TypeScript code.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/yurakawa/mskills/typescript
Clone the repo
git clone --depth 1 https://github.com/yurakawa/mskills

Made for: GitHub Copilot.

Per session 468 This file is loaded in full into every session.
When invoked 468 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00468 $0.00468
Opus 5 $0.00234 $0.00234
Sonnet 5 $0.00094 $0.00094
Haiku 4.5 $0.00047 $0.00047

Measured 2d ago against content hash deef632b4fc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mskills typescript.instructions.md 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.

.github/instructions/typescript.instructions.md · 56 lines

What it actually says

TypeScript Instructions

Module System

  • ESM Only: This project uses ES modules exclusively
  • Import Extensions: Always use .js extensions when importing local modules, even for .ts files
    • import { config } from './config/index.js'
    • import { config } from './config/index'
    • import { config } from './config/index.ts'

Type Safety

  • Strict Mode: TypeScript strict mode is enabled - maintain type safety
  • No Implicit Any: Avoid implicit any types
    • Use explicit types for function parameters and return values
    • Use unknown instead of any when type is uncertain, then narrow with type guards
  • Type Imports: Use import type for type-only imports to avoid runtime overhead
    • import type { Command } from 'commander'

Node.js APIs

  • Node Imports: Use the node: protocol for built-in modules
    • import fs from 'node:fs/promises'
    • import path from 'node:path'
    • import os from 'node:os'
  • Async/Await: Use promises and async/await for file system operations

Error Handling

  • Type Errors: When catching errors, type them as any or use type guards
    try {
      // code
    } catch (error: any) {
      console.error(chalk.red(`Error: ${error.message}`));
    }
    

Zod Schemas

  • Use Zod for runtime validation of external data (config files, user input)
  • Define TypeScript types from Zod schemas: type Config = z.infer<typeof configSchema>
  • Provide sensible defaults with .default() for optional fields

Testing

  • Test files should be co-located with source files: manager.test.ts next to manager.ts
  • Use Vitest's vi.mock() for mocking dependencies
  • Import from compiled .js files when needed in tests
Changes

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.

  1. 2d ago First seen · 56 lines · 468 tokens per session scan A deef632b4fc4

Subscribe to this mod's changes

mskills typescript.instructions.md is an instructions file published in the GitHub repository yurakawa/mskills (3 stars, last pushed 4mo ago), licensed MIT. It adds 468 tokens to every session, about $0.0023 per session on Opus 5. 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.