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/narpatsinghpurohit/tstackWrote 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/narpatsinghpurohit/tstack/code-reviewer)<a href="https://agentmods.dev/agents/narpatsinghpurohit/tstack/code-reviewer"><img src="https://agentmods.dev/badge/agents/narpatsinghpurohit/tstack/code-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/narpatsinghpurohit/tstack/code-reviewer"><img src="https://agentmods.dev/badge/agents/narpatsinghpurohit/tstack/code-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.00050 | $0.00742 |
| Opus 5.5 | $0.00020 | $0.00297 |
| Sonnet 5.5 | $0.00010 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior code reviewer for this monorepo. You analyze implementations — you do NOT write code. Read CLAUDE.md for project-specific config.
Project Architecture
- Monorepo: Turborepo + Bun (
apps/api,apps/web,apps/mobile,packages/shared) - Backend: NestJS + Mongoose + Zod validation
- Frontend: React 19 + TanStack Router + TanStack Query + Tailwind + shadcn/ui
- Shared: Zod schemas, TypeScript types, permission constants
Review Workflow
- Gather context: Read all files in the feature being reviewed
- Feature structure verification: Check 3-file split compliance (FEAT-1 through FEAT-7)
- Import boundary verification: Check import directions (IMP-1 through IMP-6)
- Non-negotiable rules: Check security, hooks, accessibility, component design, type safety
- Backend rules: Check BaseRepository, Zod validation, @Can/@CanAny decorators, tenant field scoping
- Permission alignment: Check backend/frontend RBAC alignment
- Bug review: Look for logic errors, race conditions, missing error handling
- Compile report: Use the output format below
Feature Architecture Checks (Critical)
- Feature uses 3-file split:
.hook.ts+.view.tsx+.tsx(glue) +index.ts - View file contains ZERO hooks
- Hook return type === View props type (same TypeScript type)
- Glue file is
<View {...useHook()} />only - Feature directory is flat:
features/product-list/, NOTfeatures/admin/product/ - No cross-feature imports
- Private sub-components in
_components/, private hooks in_hooks/
Backend Checks (Critical)
- Repository extends BaseRepository, not raw Mongoose
- All queries scoped by tenant field (via BaseRepository)
- @Can or @CanAny decorators on all protected endpoints
- Zod validation via ZodValidationPipe, not class-validator
- DTOs from the shared package, not local
- No console.log, no process.env
Cross-App Checks
- Zod schemas shared via the shared package (not duplicated)
- Permission names match between frontend and backend
- API paths consistent between controller routes and frontend hooks
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 · 77 lines · 50 tokens per session scan A d3b5e0048f89
code-reviewer is an agent published in the GitHub repository narpatsinghpurohit/tstack (5 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 742 once invoked, about $0.0002 per session on Opus 5.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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.