servalsheets: Agent for Claude Code

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

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

An automated code-review workflow that checks source code from several angles, including types, formatting rules, security, tests, API practices, and project-specific consistency.

In plain words
What is it for?
Use it before committing changes to review code, run project checks, inspect test coverage, detect unsafe patterns, and verify that schemas, handlers, and integrations remain aligned.
Why use it?
It brings many pre-commit checks into one review so problems can be found before the code reaches continuous integration, the automated checks that run after changes are submitted.

Agent for Claude Code

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

This is khill1269/servalsheets's own configuration. It tells Claude Code how to work on servalsheets 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 configures →

Reuse

Borrowing it

Nothing to install: this file belongs to khill1269/servalsheets. 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/main/.claude/agents/code-review-orchestrator.md
Clone the repo
git clone --depth 1 https://github.com/khill1269/servalsheets

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/code-review-orchestrator/github.svg)](https://agentmods.dev/agents/khill1269/servalsheets/code-review-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/khill1269/servalsheets/code-review-orchestrator"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/code-review-orchestrator/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.

agentmods 80×15 button for code-review-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/khill1269/servalsheets/code-review-orchestrator"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/code-review-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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,537 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 original No closer match found 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.01537
Opus 5.5 $0.00024 $0.00615
Sonnet 5.5 $0.00012 $0.00307
Haiku 4.5 $0.00006 $0.00154

Measured 2mo ago against content hash c0ae5c28cc0a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-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 2mo 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

Copies of this mod

1 near-identical copy found in the catalogue:

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

How it starts

The opening of the file, as written. The whole thing — 196 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

  • 25 tools, 410 actions, MCP 2025-11-25 protocol
  • Handlers: src/handlers/*.ts — 13 extend BaseHandler, 12 standalone; all 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 (~30s)

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
npm run validate:alignment 2>&1        # Schema-handler alignment (25 tools)
npm run check:integration-wiring 2>&1  # Mutation action wiring
npm run check:mutation-actions 2>&1    # MUTATION_ACTION_NAMES consistency

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 (MCP 2025-11-25)

Check every handler/schema change:

  • Tool names must be snake_case — not camelCase; 1–128 chars, A-Za-z0-9_-. only (SEP-986)
  • 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
  • Tool annotation fields use Hint suffix: readOnlyHint, destructiveHint, idempotentHint, openWorldHint — NOT readOnly etc. Verify in src/mcp/registration/flat-tool-registry.ts
  • Long-running new actions (>5s) must declare execution.taskSupport: 'optional' in src/mcp/features-2025-11-25.ts and src/generated/annotations.ts
  • New elicitation calls that handle OAuth, API keys, or sensitive creds MUST use mode: "url" (not form mode)
  • Input validation errors use isError: true in CallToolResult (tool-level errors), NOT -32602 JSON-RPC errors (SEP-1303)

Read the full file on GitHub · 196 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. 2mo ago First seen · 196 lines · 59 tokens per session scan A c0ae5c28cc0a

Subscribe to this mod's changes

code-review-orchestrator is an agent published in the GitHub repository khill1269/servalsheets (0 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,537 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.

Related

Other agents, from other repositories

agent-reviewer

Use this agent when reviewing agent code for quality and best practices. Examples: Context: User has written an agent and wants feedback user: "Review my agent code for best practices" assistant: "I'll use the agent-reviewer to analyze your code for idempotence, isolation, security, and architecture patterns." User…

comet-ml/opik-claude-code-plugin · 225 tokens

unused-code-reviewer

Reviews the whole repository for unused and dead artifacts: unreferenced code and exports, unreachable branches, orphaned files, dead tests and fixtures, unused CI jobs and workflow inputs, unreferenced infrastructure and container config, obsolete migrations, flags, dependencies, docs, and assets. Spawn when user…

RashadAnsari/myagents · 96 tokens

code-reviewer

Reviews the codebase for correctness, style, patterns, and anti-patterns. Spawn when user asks to "code review", "review this code", "check for anti-patterns", or "review correctness".

RashadAnsari/myagents · 46 tokens

database-reviewer

Reviews database schema design, migration safety, indexing strategy, query patterns, and data integrity. Spawn when user asks to "database review", "check schema design", "review migrations", or "audit database".

RashadAnsari/myagents · 45 tokens

commit-pusher

Commits and pushes changes. Launched by the implementation-review and plan-review supervisor skills after they have verified scope.

MarcusJellinghaus/mcp-tools-py · 27 tokens

satd-analyst

Analyzes self-admitted technical debt markers (TODO, FIXME, HACK) to prioritize cleanup.

panbanda/omen · 26 tokens