ts-strict

A guided command for enabling TypeScript strict mode in stages. Strict mode turns on checks that catch more possible mistakes in TypeScript code.

In plain words
What is it for?
Use it to inspect current strictness, enable the next strict setting, group resulting errors, apply common fixes, and plan the remaining manual work.
Why use it?
It breaks a potentially large set of type errors into smaller groups and offers fixes for common patterns while showing what needs human judgment.

Command

Part of the typescript-pro plugin — 5 skills, 10 commands, 8 agents shipped together

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 commands/andronics/claude-plugin-typescript-pro/ts-strict
Clone the repo
git clone --depth 1 https://github.com/andronics/claude-plugin-typescript-pro

Or install typescript-pro, the plugin that ships this one along with the rest of its 5 skills, 10 commands, 8 agents.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 431 The whole file, excluding the scripts and references it only reads on demand.
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.00010 $0.00431
Opus 5 $0.00005 $0.00216
Sonnet 5 $0.00002 $0.00086
Haiku 4.5 $0.00001 $0.00043

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

Security

Grade A, and why

ts-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 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.

commands/ts-strict.md · 59 lines

What it actually says

Enable TypeScript strict mode incrementally with automated fixes and guidance:

  1. Analyze Current State

    • Check current tsconfig.json strict settings
    • Run type checker to count existing errors
    • Identify which strict flags are disabled
    • Estimate migration effort for each flag
  2. Propose Migration Plan

    • Present current strict mode status
    • Recommend order of strict flag adoption:
      1. noImplicitAny
      2. strictNullChecks
      3. strictFunctionTypes
      4. strictBindCallApply
      5. strictPropertyInitialization
      6. noImplicitThis
      7. alwaysStrict (usually no impact)
    • Show estimated file count affected by each flag
  3. Enable Next Strict Flag

    • Enable the next recommended strict flag in tsconfig.json
    • Run type checker to identify errors
    • Group errors by file and error type
    • Show summary of errors to fix
  4. Provide Automated Fixes

    • Offer to fix common patterns automatically:
      • Add explicit types for implicit any
      • Add null checks with optional chaining
      • Initialize class properties
      • Add type guards for narrowing
    • Show diffs before applying fixes
  5. Guide Manual Fixes

    • For errors requiring human judgment:
      • Explain the error in plain English
      • Show the problematic code with context
      • Suggest multiple fix approaches
      • Provide code examples
  6. Iterate Until Strict

    • After fixing current flag's errors, verify with tsc
    • Move to next strict flag
    • Track progress toward full strict mode
    • Celebrate when strict: true is achieved!
  7. Create Migration PR

    • Commit changes with clear message
    • Generate PR description with migration summary
    • List all strict flags now enabled
    • Document any remaining TODOs

Use this command repeatedly to incrementally adopt strict mode without overwhelming the codebase with errors.

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 · 59 lines · 10 tokens per session scan A cda40defd0b4

Subscribe to this mod's changes

ts-strict is a command published in the GitHub repository andronics/claude-plugin-typescript-pro (4 stars, last pushed 10mo ago), licensed MIT. It adds 10 tokens to every session and 431 once invoked, about $0.0001 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.