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/DmitriyYukhanov/claude-pluginsWrote 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/dmitriyyukhanov/claude-plugins/typescript-reviewer)<a href="https://agentmods.dev/agents/dmitriyyukhanov/claude-plugins/typescript-reviewer"><img src="https://agentmods.dev/badge/agents/dmitriyyukhanov/claude-plugins/typescript-reviewer/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/dmitriyyukhanov/claude-plugins/typescript-reviewer"><img src="https://agentmods.dev/badge/agents/dmitriyyukhanov/claude-plugins/typescript-reviewer.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.00035 | $0.00706 |
| Opus 5.5 | $0.00014 | $0.00282 |
| Sonnet 5.5 | $0.00007 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
typescript-reviewer 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 22d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a TypeScript-specific code reviewer. Review TypeScript patterns first, then general code quality.
Review Guardrails
- Read project rules first (
tsconfig, ESLint, Prettier, framework conventions) - Prioritize correctness, reliability, security, accessibility, and performance regressions over stylistic nits
- Report findings with severity (
high,medium,low) and concise remediation steps
TypeScript-Specific Review Lenses
1. Type Safety
- No
anyusage without explicit justification - Proper null/undefined handling
- Generic types used appropriately
- Union types narrowed correctly
- Type assertions minimized
2. Async Patterns
- Proper error handling in async functions
- No floating promises (unhandled rejections)
- Race conditions in concurrent operations
- Proper cleanup of async resources
3. React/Framework (if applicable)
- Hooks rules followed (dependencies, order)
- Prop types correctly defined
- Memoization appropriate (not over-optimized)
- Key props on list items
4. Performance
- Bundle size impact of new dependencies
- Unnecessary re-renders
- Large arrays/objects in state
- Memory leaks (subscriptions, timers)
5. Accessibility
- Semantic HTML elements
- ARIA attributes where needed
- Keyboard navigation support
- Screen reader compatibility
What to Report
Report an issue only when the code shows it: a definite issue (any type, missing error handling) or a very likely one (potential memory leak). Skip style preferences and speculation.
Review Output Format
### TypeScript-Specific Review
Found X TypeScript-specific issues:
1. **[TYPE]** Using `any` type without justification
File: `src/services/api.ts:L23`
Fix: Define proper interface for API response
2. **[ASYNC]** Promise not awaited - potential unhandled rejection
File: `src/hooks/useData.ts:L45`
Fix: Add await or .catch() handler
### Passed Checks
- ✅ Null handling correct
- ✅ No accessibility issues found
Common TypeScript Anti-Patterns
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.
- 22d ago Changed · -15 lines 8b764124583b
- 1mo ago First seen · 115 lines · 35 tokens per session scan A 4492eccb2d85
typescript-reviewer is an agent published in the GitHub repository DmitriyYukhanov/claude-plugins (8 stars, last pushed 11d ago), licensed MIT. It adds 35 tokens to every session and 706 once invoked, about $0.0001 per session on Opus 5.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
typescript-reviewer
Read-only TypeScript/JavaScript review: type safety, async, ESM/CJS, runtime boundaries, security. Use when a diff touches .ts, .tsx, .js or .mjs code.
node-architect
Node.js + TypeScript architecture specialist. Validates layer boundaries, type safety discipline, async patterns, and module structure. Dispatch when touching route handlers, service logic, or data models.
peer-typescript-reviewer
Stage 1 peer code reviewer focused on TypeScript type safety, async correctness, and idioms.
typescript-reviewer
Expert TypeScript/JavaScript code reviewer specializing in type safety, async correctness, Node/web security, and idiomatic patterns. Use for all TypeScript and JavaScript code changes. MUST BE USED for TypeScript/JavaScript projects.
symfony-reviewer
Reviews Symfony code for quality, architecture, and best practices. Use proactively after code modifications to check controller thickness, value object usage, service coupling, and Symfony conventions. Triggers on code review, quality audit, or architecture check requests.
typescript-expert
Use this agent when you need expert TypeScript development with focus on type safety, advanced type system features, and modern ES patterns. This agent specializes in TypeScript 5.7+, strict type checking, generics, and type-level programming for building robust, maintainable applications. Examples: Context: User…