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/google-api-architectgit clone --depth 1 https://github.com/khill1269/servalsheetsWrote 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/google-api-architect)<a href="https://agentmods.dev/agents/khill1269/servalsheets/google-api-architect"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/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.02860 |
| Opus 5 | $0.00227 | $0.01430 |
| Sonnet 5 | $0.00091 | $0.00572 |
| Haiku 4.5 | $0.00045 | $0.00286 |
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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- google-api-architect — 97% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 232 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 (25 tools, 410 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.
- 2d ago First seen · 232 lines · 454 tokens per session scan A c1e6613457b1
google-api-architect is an agent published in the GitHub repository khill1269/servalsheets (0 stars, last pushed 10d ago), licensed MIT. It adds 454 tokens to every session and 2,860 once invoked, about $0.0023 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 agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
chainaware-rug-pull-detector
Specialized Web3 rug pull detection agent powered by ChainAware's Behavioral Prediction MCP. Use this agent PROACTIVELY whenever a user wants to check if a smart contract, liquidity pool, DeFi token, or new project is safe to invest in or deposit funds into. Automatically invoke when the user provides a contract…
onboarding
Onboard new projects with zen analysis configuration.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.