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 skills/cablate/mcp-google-map/project-docsnpx skills add cablate/mcp-google-map --skill project-docsgit clone --depth 1 https://github.com/cablate/mcp-google-mapWhat 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.00049 | $0.00733 |
| Opus 5 | $0.00024 | $0.00367 |
| Sonnet 5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
mcp-google-map-project 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 yesterday.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcp-google-map — Project Knowledge
Overview
This skill contains everything needed to develop, maintain, and extend the @cablate/mcp-google-map MCP server. Reading these files gives you full context on architecture, API specifics, domain knowledge, and the reasoning behind design decisions.
For the agent skill (how to USE the tools), see skills/google-maps/SKILL.md.
Quick Orientation
| Aspect | Summary |
|---|---|
| What | MCP server providing Google Maps tools for AI agents |
| Stack | TypeScript, Node.js, Express, MCP SDK, Zod |
| Tools | 17 tools (14 atomic + 3 composite) |
| Transports | stdio, Streamable HTTP, standalone exec CLI |
| APIs | Places API (New), Directions, Geocoding, Elevation, Timezone, Weather, Air Quality, Static Maps, Search Along Route |
Reference Files
| File | Content | When to read |
|---|---|---|
references/architecture.md |
System architecture, 3-layer design, transport modes, tool registration flow, 9-file checklist, code map | Start here when onboarding. Also read when adding new tools. |
references/google-maps-api-guide.md |
All Google Maps API endpoints used, pricing, coverage limits, rate limits, common gotchas, Places New vs Legacy | When debugging API errors, evaluating new APIs, or checking costs |
references/geo-domain-knowledge.md |
GIS fundamentals — coordinates, distance, geocoding, place types, spatial search, map projection, Japan-specific knowledge | When making tool design decisions that involve geographic concepts |
references/decisions.md |
10 Architecture Decision Records (ADR) with context and rationale | When asking "why was X built this way?" or considering changes to existing design |
How to Add a New Tool
See references/architecture.md § "9-File Tool Change Checklist" for the complete procedure. Summary:
- Create
src/tools/maps/<toolName>.ts(NAME, DESCRIPTION, SCHEMA, ACTION) - Register in
src/config.ts - Add exec case in
src/cli.ts - Add to
tests/smoke.test.ts(expectedTools + API call test) - Update
README.md(count + table + exec list + project structure) - Update
skills/google-maps/SKILL.md(Tool Map) - Update
skills/google-maps/references/tools-api.md(params + chaining) - Check
server.jsonandpackage.jsondescriptions
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 67 lines · 49 tokens per session scan A f2aaa0ae7094
mcp-google-map-project is a skill published in the GitHub repository cablate/mcp-google-map (438 stars, last pushed 15d ago), licensed MIT. It adds 49 tokens to every session and 733 once invoked, about $0.0002 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-30.
Other skills, from other repositories
baocut
BaoCut-only operator for the installed bcut CLI and .bcut projects. Implicitly trigger only when the request explicitly names BaoCut or bcut, targets a .bcut project or BaoCut Subtitle Studio, or continues a BaoCut workflow already established in the conversation. Do not trigger solely for generic audio or video…
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
proxies
Oxylabs proxy networks: Residential, Mobile, shared Datacenter/ISP, and Dedicated Datacenter/ISP proxies with geo-targeting, IP rotation, session persistence, and port-based sticky IPs. Use when routing traffic through proxies, building scrapers with proxy auth, rotating or sticky sessions, whitelisting IPs, or…
agentsop-llamaindex
Operating-system distillation of LlamaIndex — the leading RAG / document-agent framework. Activate when the calling agent must build, debug, harden, or evaluate a Retrieval-Augmented Generation pipeline over unstructured/private data, decide between RAG primitives (Index types, retrievers, query engines, routers…
agentsop-prompt-compilation
The compile-readiness gate for prompt auto-optimization. Decide whether you have earned the right to run an optimizer (DSPy MIPROv2 / GEPA / BootstrapFewShot) before spending compute. Two preconditions only — a real metric, and enough examples for the optimizer you picked. Garbage metric in, garbage prompt out. Pick…
agentsop-signature-design
Decision rubric for promoting a prose prompt into a typed DSPy Signature. This is an ENHANCE overlay on top of the [[dspy]] library skill: it does NOT teach DSPy syntax — it answers the coder-agent decision "when do I stop hand-writing a prompt string and declare it as a dspy.Signature, and how do I name/describe its…