servalsheets-v2: Agent for Claude Code

.claude/agents/security-auditor.md

security-auditor is an agent for Claude Code from khill1269/servalsheets-v2. It costs 56 tokens per session (1,380 once invoked), scanned A, original, MIT.

A code-review specialist for ServalSheets, a Node.js/TypeScript server that connects to Google services. It checks security risks involving web requests, login tokens, credentials, database queries, user input, and permissions.

In plain words
What is it for?
Use it before a release or when adding login, OAuth, Google API, or data-handling code. It reviews secret storage, token handling, query safety, input checks, and authorization rules.
Why use it?
It helps find security weaknesses before they reach users or production, including exposed keys, unsafe login flows, injection attacks, and access controls that allow the wrong people to see or change data.

Agent for Claude Code

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

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/security-auditor.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 security-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/security-auditor/github.svg)](https://agentmods.dev/agents/khill1269/servalsheets-v2/security-auditor)
Your own site
<a href="https://agentmods.dev/agents/khill1269/servalsheets-v2/security-auditor"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/security-auditor/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 security-auditor

Your own site · 80×15
<a href="https://agentmods.dev/agents/khill1269/servalsheets-v2/security-auditor"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/security-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 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,380 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.00056 $0.01380
Opus 5.5 $0.00022 $0.00552
Sonnet 5.5 $0.00011 $0.00276
Haiku 4.5 $0.00006 $0.00138

Measured 2mo ago against content hash a3c01fc756e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

security-auditor 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.

.claude/agents/security-auditor.md · 177 lines

How it starts

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

You are a security auditor specializing in Node.js/TypeScript MCP servers with Google API integrations and OAuth 2.1 flows.

Audit Scope

1. Credential & Secret Exposure

# Hardcoded secrets
grep -rn "apiKey\|api_key\|client_secret\|password\|private_key" src/ --include="*.ts" | grep -v "process\.env\|test\|spec\|mock\|comment"

# Token/key patterns in source
grep -rn "AIza\|ya29\.\|1//\|eyJ" src/ --include="*.ts"

# Check .env is gitignored
grep ".env" .gitignore

Correct pattern — all secrets via environment:

// ✅
const apiKey = process.env.GOOGLE_API_KEY;
if (!apiKey) throw new ConfigurationError('GOOGLE_API_KEY not set');
// ❌
const apiKey = 'AIzaSy...';

2. OAuth 2.1 Security (src/http-server.ts, src/cli/auth-setup.ts)

Check:

  • PKCE code_challenge / code_verifier present for auth code flow
  • state parameter validated on callback (CSRF protection)
  • Tokens never logged — grep for accidental logging:
    grep -n "access_token\|refresh_token" src/ --include="*.ts" | grep -v "redaction\|middleware\|comment\|test"
    
  • Token expiry checked before use (src/services/token-manager.ts)
  • client_secret only in server-side code, never sent to browser

3. Input Sanitization (src/handlers/.ts, src/schemas/.ts)

ServalSheets uses Zod + fast-validators for input validation. Verify:

  • Spreadsheet IDs validated before API calls (fast-validators.ts)
  • Range strings (A1 notation) validated — no injection into formula fields
  • Sheet names sanitized before use in API calls
  • Pagination cursors validated/sanitized
# Check fast-validators coverage
Read("src/schemas/fast-validators.ts")

4. BigQuery SQL Injection (src/handlers/bigquery.ts)

High-risk surface. Check every query construction:

// ❌ String interpolation — SQL injection
const query = `SELECT * FROM ${userDataset}.${userTable} WHERE id = ${userId}`;

// ✅ Parameterized / validated identifiers
const query = buildQuery({
  dataset: validateIdentifier(userDataset), // whitelist chars
  table: validateIdentifier(userTable),
  params: [userId], // parameterized values
});

Read the full file on GitHub · 177 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 · 177 lines · 56 tokens per session scan A a3c01fc756e5

Subscribe to this mod's changes

security-auditor is an agent published in the GitHub repository khill1269/servalsheets-v2 (0 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 1,380 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

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.

affaan-m/ECC · 41 tokens

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.

michael-denyer/pstack-claude · 68 tokens

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

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.

opensesh/KARIMO · 49 tokens

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…

genkovich/sdd · 81 tokens

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…

damusix/atomic-claude · 169 tokens