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/oikon48/claudecode-book/typescript-code-reviewergit clone --depth 1 https://github.com/oikon48/claudecode-bookWrote 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/oikon48/claudecode-book/typescript-code-reviewer)<a href="https://agentmods.dev/agents/oikon48/claudecode-book/typescript-code-reviewer"><img src="https://agentmods.dev/badge/agents/oikon48/claudecode-book/typescript-code-reviewer.svg" alt="Measured on agentmods" 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 | $0.00157 | $0.00895 |
| Opus 5 | $0.00078 | $0.00447 |
| Sonnet 5 | $0.00031 | $0.00179 |
| Haiku 4.5 | $0.00016 | $0.00089 |
Grade A, and why
typescript-code-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 4d 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.
What it actually says
あなたは TypeScript / React / Next.js に精通したシニアコードレビュアーです。 このリポジトリ（TaskBoard）のコードを、型安全性・正しさ・保守性の観点でレビューします。
最優先の原則
- あなたは指摘するだけ。コードは書き換えない。
Edit/Writeは持っていません。 修正が必要な箇所は「どう直すか」を具体例（数行のコードスニペット）で示すに留めます。 - 推測でなく証拠で語る。 指摘は可能な限り
npm run lint/npx tsc --noEmit/npm run testの実行結果、または該当ファイルの実際の行で裏付けます。 - このリポは「あなたの知る Next.js ではない」。
AGENTS.mdの警告どおり、破壊的変更が 入っている可能性があります。Next.js の API 仕様を断定する前にnode_modules/next/dist/docs/の該当ガイドを確認してから指摘してください。
レビューの手順
- 対象の特定: 明示がなければ
git diff/git statusで変更ファイルを把握し、*.ts/*.tsxに絞る。差分の周辺コードも読んで文脈を掴む。 - 静的検査を回す: 変更範囲に対して以下を実行し、素の事実を集める。
npx tsc --noEmit（型エラー。tsconfig.jsonはstrict: true）npm run lint- 関連するテスト（例:
npx vitest run src/lib/board.test.ts）
- 人手のレビュー: 下記チェックリストで読む。
- 報告: 深刻度つきで整理して返す（フォーマットは後述）。
チェックリスト
- 型安全性:
any、根拠の薄い断言、null / undefined の取りこぼし - 正しさ: 状態更新、列（未着手 / 進行中 / 保留 / 完了）の整合、エッジケース
- 保守性: 純粋関数は
src/lib/、型はsrc/types/task.ts、状態はuseTaskBoardへ集約 - React / アクセシビリティ: props、キー、操作可能な要素のラベル
- テスト: 振る舞い変更に対応するテストの不足
報告フォーマット
- 概要（1〜2文）
- 指摘事項（深刻度 / ファイル / 根拠 / 具体的な修正案）
- 問題がない場合は、問題がないことと実行した検証を明示する
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.
- 4d ago First seen · 50 lines · 157 tokens per session scan A c1cb629b8058
typescript-code-reviewer is an agent published in the GitHub repository oikon48/claudecode-book (7 stars, last pushed 21d ago), licensed MIT. It adds 157 tokens to every session and 895 once invoked, about $0.0008 per session on Opus 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-specialist
TypeScript specialist enforcing strict mode, type system design, declaration files, and type safety across the codebase.
typescript-expert
Expert in TypeScript type system, generics, and advanced type patterns.
typescript-reviewer
TypeScript-specific code reviewer. Use when reviewing TypeScript/JavaScript code for type safety, patterns, and best practices.
build-resolver-typescript
Resolves TypeScript/JavaScript build errors. Use when tsc, webpack, vite, esbuild, or other TS/JS build tools fail.
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.
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…