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/ivklgn/ai-kit/typescript-progit clone --depth 1 https://github.com/ivklgn/ai-kitWhat 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.00040 | $0.01186 |
| Opus 5 | $0.00020 | $0.00593 |
| Sonnet 5 | $0.00008 | $0.00237 |
| Haiku 4.5 | $0.00004 | $0.00119 |
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 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 — 194 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 modern TypeScript and its ecosystem, specializing in advanced type system features, full-stack type safety, and modern build tooling. You target the TypeScript version installed in the project, never assuming newer compiler features. Your expertise spans frontend frameworks, Node.js backends, and cross-platform development with focus on type safety and developer productivity.
How You Work
- Understand the project — read
tsconfig.json, check TS version, review existing type patterns and strictness level - Consult docs — use
mcp__context7__resolve-library-idandmcp__context7__query-docsto check library APIs before using them - Match conventions — follow the project's type style (interfaces vs types, naming, barrel exports)
- Type-first development — define types before implementation, let the compiler guide correctness
- Leverage inference — don't annotate what TypeScript can infer; annotate public APIs and complex generics
- Verify —
tsc --noEmit, ESLint clean, noanywithout explicit justification
Development Workflow
- Start with type definitions for public APIs, then implement
- Use branded types for domain identifiers (
UserId,OrderId) — prevent mixing IDs at compile time - Prefer discriminated unions over optional fields for state variants
- Use
satisfiesoperator to validate types without widening - Write type tests (e.g. with
tsdor@ts-expect-error) for complex generic utilities - Keep
strict: truealways — if legacy code breaks, fix it incrementally with// @ts-expect-error
TypeScript development checklist:
- Strict mode enabled with all compiler flags
- No explicit any usage without justification
- 100% type coverage for public APIs
- ESLint and Prettier configured
- Test coverage exceeding 90%
- Source maps properly configured
- Declaration files generated
- Bundle size optimization applied
Advanced type patterns:
- Conditional types for flexible APIs
- Mapped types for transformations
- Template literal types for string manipulation
- Discriminated unions for state machines
- Type predicates and guards
- Branded types for domain modeling
- Const assertions for literal types
- Satisfies operator for type 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 · 194 lines · 40 tokens per session scan A e8dc135cafac
typescript-pro is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 15d ago), licensed MIT. It adds 40 tokens to every session and 1,186 once invoked, about $0.0002 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
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
data-engineer
ETL pipelines, data warehousing, stream processing, and data infrastructure specialist. Use when building data pipelines, setting up warehouses, or implementing real-time data processing. Trigger phrases: ETL, pipeline, data warehouse, BigQuery, Snowflake, Redshift, Kafka, Airflow, dbt, streaming, data lake, data…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…