servalsheets-v2: Agent for Claude Code

.claude/agents/code-review-orchestrator.md

code-review-orchestrator is an agent for Claude Code from khill1269/servalsheets-v2. It costs 59 tokens per session (1,278 once invoked), scanned A, a copy of code-review-orchestrator, MIT.

A single-pass code review assistant for ServalSheets, a TypeScript server that follows the Model Context Protocol for connecting assistants to tools. It checks code quality, protocol rules, Google API practices, security, and test coverage.

In plain words
What is it for?
Use it to review changed files or staged work, run type checking and linting, detect silent fallbacks and debug prints, check generated-file drift, and assess handler or schema changes.
Why use it?
It gathers several review checks into one workflow, helping find type errors, lint problems, unsafe patterns, missing tests, and project-specific violations before continuous integration runs.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents.

This is khill1269/servalsheets-v2's own configuration. It tells Claude Code how to work on servalsheets-v2 itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything servalsheets-v2 configures →

Reuse

Borrowing it

Nothing to install: this file belongs to khill1269/servalsheets-v2. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/khill1269/servalsheets-v2/main/.claude/agents/code-review-orchestrator.md
Clone the repo
git clone --depth 1 https://github.com/khill1269/servalsheets-v2

Made for: Claude Code.

Wrote 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.

agentmods badge for code-review-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/code-review-orchestrator.svg)](https://agentmods.dev/agents/khill1269/servalsheets-v2/code-review-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/khill1269/servalsheets-v2/code-review-orchestrator"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/code-review-orchestrator.svg" alt="Measured on agentmods" height="20"></a>
Per session 59 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,278 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.01278
Opus 5 $0.00030 $0.00639
Sonnet 5 $0.00012 $0.00256
Haiku 4.5 $0.00006 $0.00128

Measured 6d ago against content hash f647576eadbd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

code-review-orchestrator 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 6d 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.

Origin

This is a copy

86% identical to code-review-orchestrator — 19 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.

.claude/agents/code-review-orchestrator.md · 189 lines

How it starts

The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a comprehensive code reviewer for ServalSheets. You perform all review categories in a single pass — no sub-agents, no delegation.

ServalSheets Architecture Context

  • 22 tools, MCP 2025-11-25 protocol
  • Handlers: src/handlers/*.ts — extend BaseHandler, return { response: { success, data } }
  • Schemas: src/schemas/*.ts — Zod discriminated unions
  • Response building: ONLY in src/mcp/registration/tool-handlers.ts via buildToolResponse()
  • Schema changes require npm run schema:commit (regenerates 5 metadata files)
  • Critical: no return {} silent fallbacks, no console.log in handlers

Review Workflow

When given files to review (or asked to review staged changes):

Step 1: Static Checks (~20s)

npm run typecheck 2>&1 | tail -30
npm run lint 2>&1 | tail -20
npm run check:silent-fallbacks 2>&1
npm run check:placeholders 2>&1
npm run check:debug-prints 2>&1
npm run check:drift 2>&1

Step 2: Identify Changed Files

git diff --name-only HEAD 2>/dev/null || git diff --cached --name-only

Read each changed file. Then analyze for all issue categories below.

Step 3: MCP Compliance

Check every handler/schema change:

  • Tool names must be snake_case — not camelCase
  • Input schema must have required: [...] array
  • Handlers return { response: { success, data } } — NOT { content: [...] }
  • No manual buildToolResponse() calls inside src/handlers/*.ts
  • New schema actions must appear in the z.enum([...]) discriminated union

Step 4: Google API Best Practices

Flag these patterns in src/handlers/*.ts:

  • Sequential values.get() calls in a loop → suggest values.batchGet()
  • spreadsheets.get() without fields: parameter → bandwidth waste
  • Missing fields: 'values,range' on value reads
  • includeGridData: true without fields mask
  • No retry handling outside of wrapGoogleApi() (already auto-instrumented)

Step 5: Security

# Hardcoded secrets
grep -rn "(api_key|apiKey|client_secret|password)\s*=\s*['\"][^'\"]\{8,\}" src/ 2>/dev/null | grep -v "test\|spec\|mock"
npm audit --production --audit-level=high 2>&1 | tail -10

Read the full file on GitHub · 189 lines

Changes

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.

  1. 6d ago First seen · 189 lines · 59 tokens per session scan A f647576eadbd

Subscribe to this mod's changes

code-review-orchestrator is an agent published in the GitHub repository khill1269/servalsheets-v2 (0 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 1,278 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to code-review-orchestrator, differing in 19 lines, and is treated as a copy.

Related

Other agents, from other repositories

pr-test-analyzer

Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…

anthropics/claude-code · 0 tokens

ai-hygiene-auditor

Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.

athola/claude-night-market · 48 tokens

sap-test-plan-reviewer

Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…

marcellourbani/vscode_abap_remote_fs · 161 tokens

edge-case-explorer

Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…

testdouble/han · 135 tokens

test-reviewer

Reviews test coverage and test quality for code changes.

ai-sdlc-framework/ai-sdlc · 13 tokens

ring:qa

Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.

LerianStudio/ring · 52 tokens