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/Fmarzochi/EGCWrote 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/fmarzochi/egc/typescript-reviewer)<a href="https://agentmods.dev/agents/fmarzochi/egc/typescript-reviewer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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/fmarzochi/egc/typescript-reviewer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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.00051 | $0.01798 |
| Opus 5.5 | $0.00020 | $0.00719 |
| Sonnet 5.5 | $0.00010 | $0.00360 |
| Haiku 4.5 | $0.00005 | $0.00180 |
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` This is a copy
97% identical to typescript-reviewer — 52 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 — 114 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.
- 1mo ago First seen · 114 lines · 51 tokens per session scan A faa2d8127b9a
typescript-reviewer is an agent published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 1,798 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 97% identical to typescript-reviewer, differing in 52 lines, and is treated as a copy.
Other agents, from other repositories
effect-ts-enforcer
Reviews a diff or file set against the 5 non-negotiables (Effect TS default, no Zod, tagged errors mapped in tagToTRPC, no process.env, unit test for every helper/repo). One line per violation, severity-tagged, no praise. Use AFTER writing code and BEFORE /verify-done. Examples — "review my changes to…
ts-enforcer
TypeScript strict mode enforcement — no any types, schema-first at trust boundaries, type vs interface discipline, strict tsconfig audit.
angular-reviewer
Angular 22 and TypeScript code review specialist — Signals, Signal Forms (stable), standalone components, RxJS, performance, zoneless change detection, httpResource.
typescript-software-architect-review
Expert TypeScript software architect that provides Clean Architecture, Domain-Driven Design (DDD), Node.js patterns, and modern TypeScript frameworks guidance. Reviews TypeScript codebases for architectural integrity, proper separation of concerns, and best practices across Express, Fastify, NestJS, and other…
type-safety-auditor
TypeScript type-safety auditor for any leakage, unsound casts, missing boundary validation and non-exhaustive handling. TRIGGER WHEN: dispatched by the type-safety audit of type-safety-rules (run by /daodan:check-health) or by senior-review in /daodan:review-changes and /daodan:review-branch; auditing TypeScript…
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.