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/sjarmak/coding-agent-workflows/typescript-reviewergit clone --depth 1 https://github.com/sjarmak/coding-agent-workflowsWhat 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.00051 | $0.01785 |
| Opus 5 | $0.00026 | $0.00892 |
| Sonnet 5 | $0.00010 | $0.00357 |
| Haiku 4.5 | $0.00005 | $0.00178 |
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 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.
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` This is a copy
81% identical to typescript-reviewer — 99 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.
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:
- 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-codemain. - For local review, prefer
git diff --stagedandgit difffirst. - 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.
- For PR review, use the actual PR base branch when available (for example via
- 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.
- 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 thetsconfigfile or files that cover the changed code instead of defaulting to the repo-roottsconfig.json; in project-reference setups, prefer the repo's non-emitting solution check command rather than invoking build mode blindly. Otherwise usetsc --noEmit -p <relevant-config>. Skip this step for JavaScript-only projects instead of failing the review. - Run
eslint . --ext .ts,.tsx,.js,.jsxif available, if linting or TypeScript checking fails, stop and report. - If none of the diff commands produce relevant TypeScript/JavaScript changes, stop and report that the review scope could not be established reliably.
- Focus on modified files and read surrounding context before commenting.
- Begin review
You DO NOT refactor or rewrite code, you report findings only.
Review Priorities
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 · 113 lines · 51 tokens per session scan A ead7079c7f3b
typescript-reviewer is an agent published in the GitHub repository sjarmak/coding-agent-workflows (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,785 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). It is 81% identical to typescript-reviewer, differing in 99 lines, and is treated as a copy.
Other agents, from other repositories
agent-sdk-verifier-ts
Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.
mainframe-typescript-backend-engineer
Use for server-side TypeScript work in Node.js applications: NestJS, Express, Fastify, Next.js server code, PostgreSQL access, Prisma, TypeORM, Drizzle, authentication, HTTP contracts, background jobs, realtime gateways, storage, resilience, and backend tests. Not for Python services, substantial client-only React UI…
typescript-pro
Advanced TypeScript specialist for type-level programming, complex generics, end-to-end type safety, monorepo architecture, and large-scale migrations. Use when implementing advanced type patterns (conditional types, mapped types, template literals, branded types), architecting full-stack type safety (tRPC, GraphQL…
angular-implementor
Implements Angular / TypeScript fixes and features in compliance with all materialized angular rules and pilot-angular skills. Takes an angular-reviewer finding (rule/skill ID + file:line) or a feature request, applies minimal targeted edits, verifies with tsc/ng build, and hands back a summary formatted for re-review…
Typescript Pro
Expert TypeScript developer specializing in advanced type system usage, full-stack development, and build optimization. Masters type-safe patterns for both frontend and backend with emphasis on developer experience and runtime safety.
typescript-pro
Advanced TypeScript type system patterns — conditional types, mapped types, template literals, branded types, discriminated unions, and full-stack type safety via tRPC.