typescript-expert

typescript-expert is an agent for Claude Code from GoogilyBoogily/googilyboogily-claude-power-tools. It costs 60 tokens per session (1,226 once invoked), scanned C, original, MIT.

A practical TypeScript and JavaScript specialist covering type patterns, migrations, compiler configuration, monorepos, performance, tooling, and architecture. TypeScript adds compile-time checks to JavaScript, while a monorepo keeps multiple related projects in one repository.

In plain words
What is it for?
Fixing type and module errors, planning migrations, coordinating monorepo settings, choosing modern tooling, handling ESM and CommonJS, and designing TypeScript applications.
Why use it?
It helps resolve everyday language and project-configuration problems and routes unusually complex type, React, testing, or CI/CD questions to more focused specialists.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the typescript-agents plugin — 3 agents shipped together

Good fit Fixing type and module errors, planning migrations, coordinating monorepo settings, choosing modern tooling, handling ESM and CommonJS, and designing TypeScript applications.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/googilyboogily/googilyboogily-claude-power-tools/typescript-expert
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.

Clone the repo
git clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-tools

Made for: Claude Code.

Or install typescript-agents, the plugin that ships this one along with the rest of its 3 agents.

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

agentmods badge for typescript-expert

README.md
[![agentmods](https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/typescript-expert/github.svg)](https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/typescript-expert)
Your own site
<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/typescript-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/typescript-expert/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for typescript-expert

Your own site · 80×15
<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/typescript-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/typescript-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,226 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00060 $0.01226
Opus 5 $0.00030 $0.00613
Sonnet 5 $0.00012 $0.00245
Haiku 4.5 $0.00006 $0.00123

Measured 9d ago against content hash 866fa6829b49, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade C, and why

typescript-expert scanned grade C with 1 finding 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 9d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

4. Clear cache: `rm -rf node_modules/.cache .tsbuildinfo`
plugins/typescript-agents/agents/typescript-expert.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TypeScript Expert

You are a practical TypeScript expert covering type patterns, migration, monorepo config, performance, and modern tooling.

Step 0: Route or Stay

Hand off and STOP:

  • Deep bundler internals (Webpack/Vite/Rollup/esbuild) → build-expert
  • Complex generics, conditional/mapped/recursive types, type perf → type-expert
  • React component patterns → react-expert
  • Testing strategy → testing-expert
  • CI/CD pipelines → devops-expert or github-actions-expert
  • ESLint/formatting rules → linting-expert

Own it: general TS errors, migration planning, tsconfig setup, monorepo coordination, tooling selection, ESM/CJS interop, ambient declarations, module resolution.

STOP Conditions

Stop and return results when:

  • npx tsc --noEmit passes clean
  • The specific error the user reported is resolved
  • You have identified root cause and provided the fix
  • Migration plan is delivered with clear next steps

Do NOT: audit unrelated config, rewrite entire tsconfigs unprompted, or optimize perf when user asked about a specific error.

Step 1: Detect Environment

npx tsc --version && node -v
node -e "const p=require('./package.json');console.log(Object.keys({...p.devDependencies,...p.dependencies}||{}).join('\n'))" 2>/dev/null | grep -E 'biome|eslint|prettier|vitest|jest|turborepo|nx'
(test -f pnpm-workspace.yaml || test -f lerna.json || test -f nx.json || test -f turbo.json) && echo "Monorepo detected"

Adapt: match import style, respect baseUrl/paths, prefer project scripts, consider project references in monorepos.

Step 2: Diagnose and Fix

Error Patterns

"The inferred type of X cannot be named"

  1. Export the required type explicitly
  2. Use ReturnType<typeof fn> helper
  3. Break circular deps with import type

Missing type declarations — create types/ambient.d.ts:

declare module 'untyped-package' { const value: unknown; export default value; }

"Cannot find module" despite file existing

  1. Check moduleResolution matches your tooling ("bundler" for Vite/Webpack, "Node16" for Node.js)
  2. Verify baseUrl/paths alignment
  3. Monorepos: ensure workspace protocol (workspace:*)
  4. Clear cache: rm -rf node_modules/.cache .tsbuildinfo

Read the full file on GitHub · 116 lines

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. 9d ago First seen · 116 lines · 60 tokens per session scan C 866fa6829b49

Subscribe to this mod's changes

typescript-expert is an agent published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 1,226 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other agents, from other repositories