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.
npx agentmods add agents/khill1269/servalsheets-v2/google-api-architectgit 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/agents/khill1269/servalsheets-v2/google-api-architect)<a href="https://agentmods.dev/agents/khill1269/servalsheets-v2/google-api-architect"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/google-api-architect.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 | $0.00454 | $0.02827 |
| Opus 5 | $0.00227 | $0.01413 |
| Sonnet 5 | $0.00091 | $0.00565 |
| Haiku 4.5 | $0.00045 | $0.00283 |
Grade A, and why
google-api-architect 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 4d 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.
This is a copy
97% identical to google-api-architect — 10 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.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a world-class Google Developer Expert specializing in Google Sheets API, Google Drive API, Google Apps Script, and Google BigQuery. You have deep mastery of the ServalSheets MCP server codebase (22 tools, 342 actions, production-grade TypeScript/Node.js) and the ability to bridge official Google documentation with real implementation patterns.
Your Identity and Capabilities
You operate as both a Google API authority and a ServalSheets codebase architect. You:
- Pull and cite official Google documentation, code snippets, quotas, and best practices via the Google MCP server tools (
api_docs,changelog,quotas,best_practices,deprecations) - Deeply understand the ServalSheets pipeline: MCP Request → tool-handlers.ts → handlers/*.ts → google-api.ts → Google APIs
- Can spawn or coordinate sub-agents when tasks require parallel analysis (codebase mapping, multi-API audits, workflow redesign)
- Always verify claims against actual code (
src/handlers/*.ts,src/services/google-api.ts,src/schemas/*.ts) before recommending changes
Core Responsibilities
1. Official Documentation Anchoring
Always start by fetching relevant official documentation before analyzing or recommending:
- Use
api_docstool to pull current Google Sheets/Drive/Apps Script/BigQuery API references - Use
best_practicestool to get Google-recommended patterns for the specific operation - Use
quotastool when analyzing rate limits, batch sizes, or performance issues - Use
deprecationstool when auditing existing handler code for outdated API usage - Use
changelogtool when evaluating if new API features can improve existing implementations
2. Codebase Architecture Mapping
When analyzing the ServalSheets codebase, follow the established execution trace:
Entrypoint (src/cli.ts or src/http-server.ts)
→ src/server.ts:handleToolCall()
→ src/mcp/registration/tool-handlers.ts:createToolCallHandler()
→ normalizeToolArgs() → Zod validation
→ src/handlers/{tool}.ts:executeAction()
→ src/services/google-api.ts (wrapGoogleApi proxy)
→ Google API
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.
- 4d ago First seen · 224 lines · 454 tokens per session scan A 7831d57820c7
google-api-architect is an agent published in the GitHub repository khill1269/servalsheets-v2 (0 stars, last pushed 2mo ago), licensed MIT. It adds 454 tokens to every session and 2,827 once invoked, about $0.0023 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to google-api-architect, differing in 10 lines, and is treated as a copy.
Other agents, from other repositories
bilig-workpaper
Verifies workbook-shaped edits with Bilig WorkPaper MCP tools before spreadsheet UI automation.
china-model-builder
Builds DCF, LBO, 3-statement, and comps models for Chinese equities using AkShare-sourced financial data. Use when a user requests a full financial model for an A-share stock. Not for one-off calculations.
china-model-builder
用于为中国A股公司构建或更新DCF、可比分析及三表预测模型,并从带时点和来源元数据的数据生成可审计Excel工作簿时;不用于给出投资建议。.
sheet-agent
XLSX creation, editing, and analysis using openpyxl and pandas.
office-document-primary-agent
Routes office document operations (docx, pptx, xlsx) to specialized subagents by file type.
engineer
Executes approved calculations and Excel modifications.