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.
curl -O https://raw.githubusercontent.com/khill1269/servalsheets-v2/main/CLAUDE.mdgit clone --depth 1 https://github.com/khill1269/servalsheets-v2Wrote 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/instructions/khill1269/servalsheets-v2/claude-md)<a href="https://agentmods.dev/instructions/khill1269/servalsheets-v2/claude-md"><img src="https://agentmods.dev/badge/instructions/khill1269/servalsheets-v2/claude-md.svg" alt="Measured on agentmods" 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.02947 | $0.02947 |
| Opus 5 | $0.01473 | $0.01473 |
| Sonnet 5 | $0.00589 | $0.00589 |
| Haiku 4.5 | $0.00295 | $0.00295 |
Grade A, and why
servalsheets-v2 CLAUDE.md 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 7d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Rules (ServalSheets)
Size cap: 300 lines. If this file exceeds 300 lines, move content to
docs/. Architecture reference:docs/development/ARCHITECTURE.md
Live State & Session Context
Live project state (auto-generated): @.serval/state.md Session notes (decisions, next steps): @.serval/session-notes.md Codebase deep context (all tools, MCP, API patterns): @docs/development/CODEBASE_CONTEXT.md Feature roadmap (P4 differentiators): @docs/development/FEATURE_PLAN.md
Project Overview
ServalSheets is a production-grade MCP server for Google Sheets with 25 tools and 407 actions.
Runtime: Node.js + TypeScript (strict). See src/schemas/index.ts for authoritative counts.
Core Pipeline
MCP Request → src/server.ts:handleToolCall()
→ src/mcp/registration/tool-handlers.ts:createToolCallHandler()
→ normalizeToolArgs() → Zod validation → handler.executeAction()
→ src/services/google-api.ts (auto-retry + circuit breaker)
→ buildToolResponse() → CallToolResult
Full 4-layer trace with line numbers: docs/development/ARCHITECTURE.md
Non-negotiable Workflow
- Verify before claiming — every fact needs
file:lineORcommand → output - Trace execution paths — prove reachability from entrypoint (STDIO/HTTP/Remote)
- No "fixes" without failing proof — reproduce with script or failing test first
- Minimal change policy — ≤3 src/ files unless tests require more; no refactors while debugging
- No silent fallbacks — never
return {}without logging; useErrorCodeenum - Dead code claims need proof — run
npm run validate:dead-code <file> <start> <end> - Schema-handler alignment — run
npm run validate:alignment; deviations must be insrc/schemas/handler-deviations.ts - Audit docs must validate —
npm run validate:auditwith.github/AUDIT_TEMPLATE.mdformat
Verification (single canonical reference)
# Before every commit
npm run verify # Full pipeline (typecheck + lint + test + drift + checks)
npm run verify:safe # Skips lint (use when ESLint OOMs in low-memory envs)
# After schema changes (ONE command)
npm run schema:commit # Regenerate metadata + verify + test + stage
# Quick checks (< 15 seconds each)
npm run check:drift # Metadata sync
npm run test:fast # Unit + contract tests
npm run typecheck # TypeScript strict mode
# Individual checks
npm run check:placeholders # No TODO/FIXME in src/
npm run check:debug-prints # No console.log in handlers
npm run check:silent-fallbacks # No silent {} returns
npm run validate:alignment # Schema-handler alignment
npm run validate:audit # Audit document validation
# Full gate pipeline
npm run gates # G0-G5 validation gates
npm run verify:build # Build + validate + smoke
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.
- 7d ago First seen · 273 lines · 2,947 tokens per session scan A 66b967bd26ef
servalsheets-v2 CLAUDE.md is an instructions file published in the GitHub repository khill1269/servalsheets-v2 (0 stars, last pushed 2mo ago), licensed MIT. It adds 2,947 tokens to every session, about $0.0147 per session on Opus 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.