Borrowing it
Nothing to install: this file belongs to 6547709/teslamate-mcp. 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/6547709/teslamate-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/6547709/teslamate-mcpWrote 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/6547709/teslamate-mcp/claude-md)<a href="https://agentmods.dev/instructions/6547709/teslamate-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/6547709/teslamate-mcp/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.02129 | $0.02129 |
| Opus 5 | $0.01064 | $0.01064 |
| Sonnet 5 | $0.00426 | $0.00426 |
| Haiku 4.5 | $0.00213 | $0.00213 |
Grade A, and why
teslamate-mcp 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this project is
A single-file FastMCP server (tesla.py, ~5475 lines) that exposes 38 read-only analytics tools over a TeslaMate PostgreSQL database. There is no Tesla Owner API token — every tool reads from the local TeslaMate schema (drives, charging_processes, cars, geofences, addresses, positions, etc.). Multi-car is supported via car_id; v1.2.x adds optional AMAP (高德) geocoding and QWeather (和风天气) enrichment, both of which silently no-op when keys are unset.
Default transport is stdio; set MCP_TRANSPORT=streamable-http for the Docker / HTTP deployment on port 8080.
Build & run
# Editable install (hatchling backend, requires Python ≥3.10)
cd teslamate-mcp
pip install -e .
# Run locally (stdio, used for desktop MCP clients)
python tesla.py
# Run as HTTP server (Docker / NAS)
MCP_TRANSPORT=streamable-http HTTP_PORT=8080 python tesla.py
# Docker
docker build -t teslamate-mcp:dev .
docker run --rm -p 8080:8080 \
-e TESLAMATE_DB_HOST=... -e TESLAMATE_DB_PASS=... \
-e MCP_TRANSPORT=streamable-http \
teslamate-mcp:dev
The Dockerfile builds with ARG VERSION=dev and exposes VERSION to the app — the runtime picks the version via _detect_version() (env VERSION → __version__ constant → git describe).
Tests
cd teslamate-mcp
python test_all.py # exit 0 = pass, exit 1 = failures
test_all.py runs without a real PostgreSQL — it monkeypatches tesla._query and tesla._query_one with SQL-fingerprint-keyed fakes (_fake_query / _fake_query_one at top of file). Two layers:
- Layer 1 (
test_unit,test_review_fixes,test_single_flight): pure-logic assertions covering the historical bug/perf/issue-fix points (BUG-4, PERF-1/2/4, ISSUE-1..5). - Layer 2 (
test_tools): asyncio-smoke every@mcp.tool()registered on themcpobject and assert it returns astrwithout raising.
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 · 98 lines · 2,129 tokens per session scan A eac12669eeff
teslamate-mcp CLAUDE.md is an instructions file published in the GitHub repository 6547709/teslamate-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 2,129 tokens to every session, about $0.0106 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.