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 commands/andronics/claude-plugin-typescript-pro/ts-buildgit clone --depth 1 https://github.com/andronics/claude-plugin-typescript-proWhat 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.00012 | $0.01174 |
| Opus 5 | $0.00006 | $0.00587 |
| Sonnet 5 | $0.00002 | $0.00235 |
| Haiku 4.5 | $0.00001 | $0.00117 |
Grade A, and why
ts-build 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build TypeScript project with intelligent error handling and analysis:
-
Detect Build Configuration
- Check for build tool:
- tsconfig.json → tsc
- vite.config.ts → Vite
- webpack.config.ts → webpack
- tsup.config.ts → tsup
- rollup.config.ts → Rollup
- Determine build mode: development or production
- Check for watch mode flag: $ARGUMENTS includes "--watch"
- Check for build tool:
-
Pre-Build Validation
- Verify TypeScript is installed
- Check tsconfig.json is valid
- Ensure dependencies are installed (node_modules exists)
- Clean previous build artifacts if needed
-
Type-Check First
- Run
tsc --noEmitto check types without emitting - This is fast and catches type errors early
- If type errors found, categorize them by:
- File (group errors by file)
- Error code (TS2322, TS2339, etc.)
- Severity (error vs warning)
- Run
-
Build Project
Execute appropriate build command:
- tsc:
npx tsc -p tsconfig.json - Vite:
npx vite build - webpack:
npx webpack --mode production - tsup:
npx tsup - Custom: Use npm script from package.json
Monitor build progress and capture output.
- tsc:
-
Handle Build Errors
Type Errors:
- Parse TypeScript error messages
- Group similar errors together
- For each unique error:
- Show file and line number
- Display code snippet with context
- Explain error in plain English
- Suggest specific fixes with code examples
- Offer to apply automated fixes where possible
Build Tool Errors:
- Module resolution failures
- Missing dependencies
- Configuration issues
- Asset loading problems
Runtime Errors:
- Import/export mismatches
- Circular dependencies
- Missing type declarations
-
Error Analysis & Suggestions
Common Error Patterns:
TS2322: Type Assignment Error
// Error: Type 'string | undefined' is not assignable to type 'string' const name: string = user.name; // user.name is string | undefined // Fixes: // 1. Handle undefined: const name: string = user.name ?? 'Unknown'; // 2. Use optional type: const name: string | undefined = user.name; // 3. Type guard: if (user.name) { const name: string = user.name; }TS2339: Property Does Not Exist
// Error: Property 'foo' does not exist on type 'User' // Fixes: // 1. Add property to interface // 2. Use optional chaining: user.foo?.bar // 3. Type assertion with explanation (last resort)TS7006: Implicit Any Parameter
// Error: Parameter 'x' implicitly has an 'any' type function add(x, y) { return x + y; } // Fix: Add explicit types function add(x: number, y: number): number { return x + y; } -
Build Success Analysis
If build succeeds:
- Show build time
- Display output file sizes
- Check for large bundles (warn if > 500KB)
- Show tree-shaking effectiveness (if applicable)
- List generated files and their locations
- Verify source maps were generated
-
Performance Metrics
Track and report:
- Type-checking time
- Build/bundling time
- Total time
- Output bundle sizes
- Number of modules processed
Compare with previous builds if possible.
-
Post-Build Actions
- Run automated tests if build successful
- Generate type declaration files (.d.ts)
- Update documentation if needed
- Suggest next steps (deploy, test, etc.)
-
Watch Mode
If
--watchflag provided:- Start incremental build in watch mode
- Monitor file changes
- Rebuild only changed files
- Show real-time type errors
- Track build performance over time
-
Build Optimization Suggestions
If build is slow or bundle is large:
- Suggest enabling
skipLibCheck - Recommend project references for monorepos
- Suggest code splitting strategies
- Identify large dependencies
- Recommend tree-shaking improvements
- Suggest moving to faster build tool (esbuild, swc)
- Suggest enabling
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 · 170 lines · 12 tokens per session scan A 33f733734c72
ts-build is a command published in the GitHub repository andronics/claude-plugin-typescript-pro (4 stars, last pushed 10mo ago), licensed MIT. It adds 12 tokens to every session and 1,174 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.
Other commands, from other repositories
build-fix
빌드 에러를 자동으로 분석하고 수정합니다.
test-ts
Run TypeScript tests for Solana frontends and Anchor programs.
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
setup-project
Initialize a new Bun + TypeScript backend project with best practices setup (Hono, Prisma, Biome, testing, Docker).
sdk
Create or extract TypeScript SDK.
scaffold-react
Quickly scaffold a new React + TypeScript project with Claude Code configuration.