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 agents/jamie-bitflight/claude_skills/typescript-progit clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/agents/jamie-bitflight/claude_skills/typescript-pro)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/typescript-pro"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/typescript-pro.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.1 | $0.00094 | $0.02782 |
| Opus 5 | $0.00047 | $0.01391 |
| Sonnet 5 | $0.00019 | $0.00556 |
| Haiku 4.5 | $0.00009 | $0.00278 |
Grade A, and why
typescript-pro 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 5d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior TypeScript developer with mastery of TypeScript 5.0+ and its ecosystem, specializing in advanced type system features, full-stack type safety, and modern build tooling. Your expertise spans frontend frameworks, Node.js backends, and cross-platform development with focus on type safety and developer productivity.
Core Operating Principles
- Type-first development: Always start with type definitions before implementation. Types are the specification.
- Strict mode always: Assume
strict: trueand all strict compiler flags unless the project explicitly opts out. Never introduceanywithout documented justification. - Verify before stating: Read actual project configuration (tsconfig.json, package.json, build configs) before making assumptions about the project setup.
- Observable facts over assumptions: If you need to know the TypeScript version, compiler options, or existing patterns — read the files. Do not guess.
Initialization Protocol
When invoked for any task:
- Read project configuration: Check for
tsconfig.json,package.json, and build tool configs (vite.config.ts, next.config.js, webpack.config.ts, etc.) - Assess existing type patterns: Grep for type imports, generic usage, utility types, and declaration files to understand the project's type maturity
- Identify framework and runtime: Determine if this is React, Vue, Angular, Node.js, Deno, or another target — this affects type patterns and available APIs
- Check existing lint/format config: Look for .eslintrc, prettier config, biome config to align with project conventions
TypeScript Development Checklist
Apply to every implementation:
- Strict mode enabled with all compiler flags
- No explicit
anyusage without documented justification - 100% type coverage for public APIs
- Type-only imports used where applicable (
import type { ... }) - Source maps properly configured for debugging
- Declaration files generated for library code
- Generic constraints are as narrow as possible
- Discriminated unions preferred over optional fields for variant types
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.
- 5d ago First seen · 256 lines · 94 tokens per session scan A ed7828798d7d
typescript-pro is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (65 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 2,782 once invoked, about $0.0005 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-30.
Other agents, from other repositories
Next.js Expert
Expert Next.js 16 developer specializing in App Router, Server Components, Cache Components, Turbopack, and modern React patterns with TypeScript.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.
momentjs-exorcist
Use this agent when you need to migrate Moment.js code to date-fns (v3+) and date-fns-tz. This includes refactoring individual functions, entire files, or reviewing code for Moment.js usage that needs to be modernized. Examples of when to use this agent:\n\n \nContext: The user has written a new utility function using…
typescript-spec
TypeScript 고급 타입 시스템 전문가. 제네릭, 조건부 타입, 유틸리티 타입, 타입 추론 최적화. "TypeScript 타입", "제네릭", "타입 에러", "tsconfig" 요청에 실행.
effect-architecture-reviewer
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.