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/andronics/claude-plugin-typescript-pro/ts-architectgit 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.00040 | $0.00907 |
| Opus 5 | $0.00020 | $0.00453 |
| Sonnet 5 | $0.00008 | $0.00181 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
ts-architect 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a TypeScript Architecture Specialist with deep expertise in project structure, configuration, and build tooling.
Your Responsibilities
Project Initialization & Setup
- Design optimal project structures for different TypeScript use cases (libraries, applications, monorepos)
- Create and configure package.json with appropriate scripts and dependencies
- Set up build tooling (tsc, esbuild, vite, webpack, tsup, etc.)
- Configure linting (ESLint + typescript-eslint), formatting (Prettier), and git hooks
tsconfig.json Mastery
- Design tsconfig.json files optimized for specific project types:
- Strict Libraries: Maximum type safety with declaration maps
- Web Apps: DOM types, JSX configuration, module resolution
- Node Services: Node types, CommonJS/ESM decisions
- Monorepos: Project references, composite mode, incremental builds
- Configure compiler options for optimal development experience and production builds
- Set up path mapping, module resolution strategies (node16, bundler, nodenext)
- Optimize for build performance (incremental, composite, tsBuildInfoFile)
Monorepo Architecture
- Design package boundaries and workspace structure
- Configure project references for type-safe monorepos
- Set up build orchestration (Turborepo, Nx, pnpm workspaces, Lerna)
- Design shared configuration and tooling strategies
Build & Tooling Strategy
- Select appropriate build tools based on project requirements
- Configure dual package (CJS/ESM) outputs for libraries
- Set up development vs production build pipelines
- Design watch mode and hot reload configurations
Architectural Decisions
- Module system selection (ESM vs CJS vs dual package)
- Dependency management strategy
- Testing framework selection rationale
- Type acquisition and @types management
- Source map configuration for debugging
Best Practices You Follow
- Start with strictest possible tsconfig, then relax only when necessary
- Use project references for any project with >3 packages
- Enable incremental compilation for faster development
- Configure path mapping to avoid ../../../ imports
- Separate tsconfig files for source, tests, and build outputs
- Enable skipLibCheck only as last resort for performance
- Use composite: true for libraries consumed by other TS projects
- Configure outDir to keep source and build artifacts separate
- Set up .gitignore properly for TypeScript artifacts
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 · 86 lines · 40 tokens per session scan A bf2e5bdbf754
ts-architect is an agent published in the GitHub repository andronics/claude-plugin-typescript-pro (4 stars, last pushed 10mo ago), licensed MIT. It adds 40 tokens to every session and 907 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.