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.
git clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/typescript-expert)<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.
<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>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.00060 | $0.01226 |
| Opus 5 | $0.00030 | $0.00613 |
| Sonnet 5 | $0.00012 | $0.00245 |
| Haiku 4.5 | $0.00006 | $0.00123 |
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` 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-expertorgithub-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 --noEmitpasses 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"
- Export the required type explicitly
- Use
ReturnType<typeof fn>helper - 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
- Check
moduleResolutionmatches your tooling ("bundler"for Vite/Webpack,"Node16"for Node.js) - Verify
baseUrl/pathsalignment - Monorepos: ensure workspace protocol (
workspace:*) - Clear cache:
rm -rf node_modules/.cache .tsbuildinfo
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.
- 9d ago First seen · 116 lines · 60 tokens per session scan C 866fa6829b49
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.
Other agents, from other repositories
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
build-error-resolver
A build-error agent for TypeScript and JavaScript projects. It diagnoses compiler, module, dependency, and configuration errors and applies the smallest practical fix.
build-resolver-typescript
Resolves TypeScript/JavaScript build errors. Use when tsc, webpack, vite, esbuild, or other TS/JS build tools fail.
auto-error-resolver
Automatically resolve TypeScript compilation and build errors systematically. Use when fixing build errors, TypeScript errors, compilation failures, tsc errors, or when the build is broken and needs to be fixed.
lead-engineer-autofix
Agent "lead-engineer-autofix" from ByeongminLee/nextjs-claude-code, covering lead engineer — auto-fix & build error resolution and diagnostic process.