Borrowing it
Nothing to install: this file belongs to YS-projectcalc/agent-cold-email. 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/YS-projectcalc/agent-cold-email/main/CLAUDE.mdgit clone --depth 1 https://github.com/YS-projectcalc/agent-cold-emailWrote 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/ys-projectcalc/agent-cold-email/claude-md)<a href="https://agentmods.dev/instructions/ys-projectcalc/agent-cold-email/claude-md"><img src="https://agentmods.dev/badge/instructions/ys-projectcalc/agent-cold-email/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.00604 | $0.00604 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
agent-cold-email CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Nothing is "done/working/deployed" without a concrete command's output quoted as evidence (typecheck, test, build, curl, screenshot). Test-mode ONLY: Stripe test keys, sandbox vendor adapters; NEVER wire real vendor spen How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ColdStart — CLAUDE.md (project law)
What this is
Multi-tenant cold-email infra platform, operated by the customer's own coding agent. See README.md (state), SPEC.md (canonical design), ROADMAP.md (build order/status).
Canonical docs — no sprawl
The ONLY living docs: README.md (per level), SPEC.md, ROADMAP.md, ARCHITECTURE.md, HANDOFF.md, MEMORY.md, and ACTIVATION.md (once created). NEVER create new status/audit/critique/handoff-vN docs — fold conclusions into these and delete temp working files. Adversarial panel verdicts are the one exception: frozen records under docs/adversarial/panel-NN/, allowed as they're not living docs.
README at every level
Every new directory that holds code or content gets a README.md at creation time: what it is, how to run/test it, what depends on it. A PR/commit adding a directory without one is incomplete.
Anti-slop development rules (hard rules)
a. No dead code, no commented-out blocks, no unused exports — delete, git remembers.
b. No god files — a file that grows past ~300 lines or two responsibilities gets split.
c. No duplicated logic — search for an existing implementation before writing a new one.
d. No hallucinated deps — every import must exist in package.json/lockfile; run install and build before claiming done.
e. Tests must assert behavior, not existence — no coverage theater; every bugfix ships with a test that FAILS on the old code.
f. No patches-on-patches — root-cause fixes only; if wrapping a workaround around a workaround, stop and fix the underlying defect.
g. Secrets NEVER in code or git — env/wrangler secrets only; .dev.vars and .env in .gitignore from day one.
h. Validate ALL tenant input at the boundary; per-tenant isolation is mandatory in every query/DO access (tenant_id scoping).
i. No speculative abstraction — YAGNI; build for the current phase of ROADMAP.md only.
Verification before done
Nothing is "done/working/deployed" without a concrete command's output quoted as evidence (typecheck, test, build, curl, screenshot). Test-mode ONLY: Stripe test keys, sandbox vendor adapters; NEVER wire real vendor spend — that's gated behind ACTIVATION.md (owner-hands).
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 · 31 lines · 604 tokens per session scan A f759bbdfa199
agent-cold-email CLAUDE.md is an instructions file published in the GitHub repository YS-projectcalc/agent-cold-email (1 stars, last pushed 12d ago), licensed MIT. It adds 604 tokens to every session, about $0.0030 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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).
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.
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.
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).
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.