What is lead-thermal-engine CLAUDE.md?

Project instructions for a lead-generation application serving a design and advertising studio that targets wellness, massage, and spa businesses.

Use them when working on the business collector, lead-scoring React app, CSV import, outreach-message generation, or local server that keeps the Anthropic key private.

They give the coding agent the project's purpose, data flow, protected files, and setup order so changes fit the existing application.

How chester9303026-dev/lead-thermal-engine configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to chester9303026-dev/lead-thermal-engine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/chester9303026-dev/lead-thermal-engine/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/chester9303026-dev/lead-thermal-engine

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/chester9303026-dev/lead-thermal-engine/claude-md/github.svg)](https://agentmods.dev/instructions/chester9303026-dev/lead-thermal-engine/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/chester9303026-dev/lead-thermal-engine/claude-md"><img src="https://agentmods.dev/badge/instructions/chester9303026-dev/lead-thermal-engine/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/chester9303026-dev/lead-thermal-engine/claude-md"><img src="https://agentmods.dev/badge/instructions/chester9303026-dev/lead-thermal-engine/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 675 This file is loaded in full into every session.

When invoked 675 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00675	$0.00675
Opus 5.5	$0.00270	$0.00270
Sonnet 5.5	$0.00135	$0.00135
Haiku 4.5	$0.00068	$0.00068

Measured 2mo ago against content hash 3190b28e5918, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lead-thermal-engine 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 2mo 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.

CLAUDE.md · 47 lines

How it starts

The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — Lead Thermal Engine

Context for the Claude Code agent working in this project.

What this project is

A two-part lead-generation tool for a design & advertising studio that sells websites, Instagram management, and ads to wellness / massage / spa businesses.

collector.py — pulls businesses from the Google Places API (New) and writes leads.csv (name, city, has_website, rating, reviews, phone, a chain-size heuristic). Instagram / ad / visual fields are left blank for manual enrichment on the short list of top leads.
React app (src/App.jsx) — imports leads.csv, scores each business by Need (how much they need a studio) × Fit (can they pay), ranks them, and writes a targeted outreach opener per lead. Message generation goes through server.js, a local proxy that holds the Anthropic key server-side.

Pipeline: collector.py → leads.csv → import into the app → ranked leads + openers.

Files — do NOT rewrite these, they are already wired

src/App.jsx — the engine. Calls /api/generate for message generation.
server.js — Anthropic proxy. Reads ANTHROPIC_API_KEY from .env.
vite.config.js — proxies /api → http://localhost:8787.
collector.py — reads GOOGLE_MAPS_API_KEY from .env.

Setup steps (do these in order)

Create .env by copying .env.example. Then ASK the user for their GOOGLE_MAPS_API_KEY (Google Cloud → enable "Places API (New)") and ANTHROPIC_API_KEY (console.anthropic.com). Do not invent or commit keys.
Install Node deps: npm install. If a pinned version fails, bump it to the latest compatible release and retry — do not change the project structure.
Set up Python for the collector: python3 -m venv .venv && source .venv/bin/activate && pip install -r requirements.txt (On Windows: .venv\Scripts\activate.)
Start the app: npm run dev. This runs Vite (http://localhost:5173) and the proxy (http://localhost:8787) together. Open the localhost URL.
To gather leads: edit KEYWORDS and CITIES at the top of collector.py for the user's target area, then run python collector.py (venv active). Import the resulting leads.csv in the running app.

Read the full file on GitHub · 47 lines

Changes

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.

2mo ago First seen · 47 lines · 675 tokens per session scan A 3190b28e5918

Subscribe to this mod's changes

lead-thermal-engine CLAUDE.md is an instructions file published in the GitHub repository chester9303026-dev/lead-thermal-engine (11 stars, last pushed 4mo ago), licensed MIT. It adds 675 tokens to every session, about $0.0027 per session on Opus 5.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.

lead-thermal-engine CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lead-thermal-engine CLAUDE.mdchester9303026-dev/lead-thermal-engine	Instructions file	11	4mo ago	MIT	A	675	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,685	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,086	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

lead-thermal-engine: Instructions file for Claude Code