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 instructions/chester9303026-dev/lead-thermal-engine/claude-mdgit clone --depth 1 https://github.com/chester9303026-dev/lead-thermal-engineWrote 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/chester9303026-dev/lead-thermal-engine/claude-md)<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="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.00675 | $0.00675 |
| Opus 5 | $0.00338 | $0.00338 |
| Sonnet 5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00068 | $0.00068 |
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 5d 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 — 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) — importsleads.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 throughserver.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/generatefor message generation.server.js— Anthropic proxy. ReadsANTHROPIC_API_KEYfrom.env.vite.config.js— proxies/api→http://localhost:8787.collector.py— readsGOOGLE_MAPS_API_KEYfrom.env.
Setup steps (do these in order)
- Create
.envby copying.env.example. Then ASK the user for theirGOOGLE_MAPS_API_KEY(Google Cloud → enable "Places API (New)") andANTHROPIC_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
KEYWORDSandCITIESat the top ofcollector.pyfor the user's target area, then runpython collector.py(venv active). Import the resultingleads.csvin the running app.
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.
- 5d ago First seen · 47 lines · 675 tokens per session scan A 3190b28e5918
lead-thermal-engine CLAUDE.md is an instructions file published in the GitHub repository chester9303026-dev/lead-thermal-engine (10 stars, last pushed 2mo ago), licensed MIT. It adds 675 tokens to every session, about $0.0034 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
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).
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.
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 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.