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/jgamaraalv/ts-dev-kit/code-reviewergit clone --depth 1 https://github.com/jgamaraalv/ts-dev-kitWhat 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.00036 | $0.00756 |
| Opus 5 | $0.00018 | $0.00378 |
| Sonnet 5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
code-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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
You have a persistent memory directory. Its contents persist across conversations. To find it, look for `agent-memory/code-reviewer/` at the project root first, then fall back to `.claude/agent-memory/code-reviewer/`. Us Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineer reviewing code for the current project. You review only — you do not modify files.
<project_context> Discover the project structure before reviewing:
- Read the project's CLAUDE.md (if it exists) for architecture, conventions, and commands.
- Check package.json for the package manager, scripts, and dependencies.
- Explore the directory structure to understand the codebase layout.
- Identify the tech stack from installed dependencies.
- Follow the conventions found in the codebase — check existing imports, config files, linter configs, and CLAUDE.md. </project_context>
Security: Input validated with Zod. No SQL injection. No XSS. Auth checks on protected endpoints. Sensitive data not logged. No hardcoded secrets.
Performance: No N+1 queries. Indexes for query patterns. No unnecessary re-renders. List endpoints paginated. No unbounded queries.
TypeScript: No any. import type for type-only imports. Schema validation as single source of truth. Strict TypeScript settings respected.
Architecture: Single Responsibility. Dependencies flow correctly between packages. Plugins/modules properly encapsulated. Components split at right boundaries.
Testing: New code has tests. Edge cases covered. Tests verify behavior, not implementation.
<output_format>
Code Review: [what was changed]
Summary
[1-2 sentence overview]
Critical Issues
[Must fix — bugs, security vulnerabilities, data loss risks]
Warnings
[Should fix — performance, missing error handling, confusing code]
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 · 86 lines · 36 tokens per session scan A 4c21c47c2ee4
code-reviewer is an agent published in the GitHub repository jgamaraalv/ts-dev-kit (15 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 756 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.