agentrium: Agent for Claude Code

.claude/agents/typescript-reviewer.md

typescript-reviewer is an agent for Claude Code from talayash/agentrium. It costs 51 tokens per session (1,787 once invoked), scanned A, a copy of typescript-reviewer, MIT.

A reviewer for TypeScript and JavaScript code, including browser and Node.js applications. It focuses on type safety, asynchronous code, security, and common language patterns.

In plain words
What is it for?
Use it to review TypeScript or JavaScript changes, check the appropriate branch or diff, run the project's type checks, and assess whether a pull request is ready for review.
Why use it?
It helps catch unsafe types, incorrect asynchronous behavior, security problems, and code that does not follow the project's established review process.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is talayash/agentrium's own configuration. It tells Claude Code how to work on agentrium itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentrium configures →

Reuse

Borrowing it

Nothing to install: this file belongs to talayash/agentrium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/talayash/agentrium/master/.claude/agents/typescript-reviewer.md
Clone the repo
git clone --depth 1 https://github.com/talayash/agentrium

Made for: Claude Code.

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-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/talayash/agentrium/typescript-reviewer/github.svg)](https://agentmods.dev/agents/talayash/agentrium/typescript-reviewer)
Your own site
<a href="https://agentmods.dev/agents/talayash/agentrium/typescript-reviewer"><img src="https://agentmods.dev/badge/agents/talayash/agentrium/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.

agentmods 80×15 button for typescript-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/talayash/agentrium/typescript-reviewer"><img src="https://agentmods.dev/badge/agents/talayash/agentrium/typescript-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 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,787 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod 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.00051 $0.01787
Opus 5.5 $0.00020 $0.00715
Sonnet 5.5 $0.00010 $0.00357
Haiku 4.5 $0.00005 $0.00179

Measured 1mo ago against content hash f1f175cc37b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

typescript-reviewer scanned grade A 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 1mo 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- **`child_process` with user input**: Validate and allowlist before passing to `exec`/`spawn`
Origin

This is a copy

95% identical to typescript-reviewer — 51 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/typescript-reviewer.md · 113 lines

How it starts

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

You are a senior TypeScript engineer ensuring high standards of type-safe, idiomatic TypeScript and JavaScript.

When invoked:

  1. Establish the review scope before commenting:
    • For PR review, use the actual PR base branch when available (for example via gh pr view --json baseRefName) or the current branch's upstream/merge-base. Do not hard-code main.
    • For local review, prefer git diff --staged and git diff first.
    • If history is shallow or only a single commit is available, fall back to git show --patch HEAD -- '*.ts' '*.tsx' '*.js' '*.jsx' so you still inspect code-level changes.
  2. Before reviewing a PR, inspect merge readiness when metadata is available (for example via gh pr view --json mergeStateStatus,statusCheckRollup):
    • If required checks are failing or pending, stop and report that review should wait for green CI.
    • If the PR shows merge conflicts or a non-mergeable state, stop and report that conflicts must be resolved first.
    • If merge readiness cannot be verified from the available context, say so explicitly before continuing.
  3. Run the project's canonical TypeScript check command first when one exists (for example npm/pnpm/yarn/bun run typecheck). If no script exists, choose the tsconfig file or files that cover the changed code instead of defaulting to the repo-root tsconfig.json; in project-reference setups, prefer the repo's non-emitting solution check command rather than invoking build mode blindly. Otherwise use tsc --noEmit -p <relevant-config>. Skip this step for JavaScript-only projects instead of failing the review.
  4. Run eslint . --ext .ts,.tsx,.js,.jsx if available - if linting or TypeScript checking fails, stop and report.
  5. If none of the diff commands produce relevant TypeScript/JavaScript changes, stop and report that the review scope could not be established reliably.
  6. Focus on modified files and read surrounding context before commenting.
  7. Begin review

You DO NOT refactor or rewrite code - you report findings only.

Review Priorities

Read the full file on GitHub · 113 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. 1mo ago First seen · 113 lines · 51 tokens per session scan A f1f175cc37b2

Subscribe to this mod's changes

typescript-reviewer is an agent published in the GitHub repository talayash/agentrium (46 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,787 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). It is 95% identical to typescript-reviewer, differing in 51 lines, and is treated as a copy.

Related

Other agents, from other repositories

java-reviewer

Review Java code changes against OpenMetadata backend patterns and Kafka-grade quality standards — method size limits, IntelliJ-level inspections, immutability, granular error handling, and human-readable code.

open-metadata/OpenMetadata · 40 tokens

csharp-quality

C# code quality — nullable reference types, async/await discipline, record types for DTOs, dependency injection patterns.

bdfinst/agentic-dev-team · 27 tokens

unit-test-writer

Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…

stacklok/toolhive-registry-server · 0 tokens

creational-auditor

Creational patterns auditor. Analyzes Builder, Object Pool, Factory, Abstract Factory, Singleton anti-pattern, and Prototype patterns. Called by acc:pattern-auditor coordinator.

dykyi-roman/awesome-claude-code · 42 tokens

code-reviewer

Structured code review for api-cp- and service-cp- PRs against HMCTS APIM standards. Checks generated interface compliance, MapStruct builder rule, CJSCPPUID propagation, PMD alignment, Jakarta EE, feature toggle rules, and Azure SDK patterns. No accessibility, no SonarQube, no Snyk. Human gate — must approve before…

hmcts/agentic-plugins-marketplace · 176 tokens

ai-slop-cleaner

Clean AI-generated code anti-patterns — redundant comments, one-use abstractions, over-engineering, template slop — via behavior-preserving edits verified by compile/lint.

RaNDoM6913/claude-code-superkit · 40 tokens