Borrowing it
Nothing to install: this file belongs to cmj-hub/claude-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/cmj-hub/claude-cold-email/main/AGENTS.mdgit clone --depth 1 https://github.com/cmj-hub/claude-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/cmj-hub/claude-cold-email/agents-md)<a href="https://agentmods.dev/instructions/cmj-hub/claude-cold-email/agents-md"><img src="https://agentmods.dev/badge/instructions/cmj-hub/claude-cold-email/agents-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.
<a href="https://agentmods.dev/instructions/cmj-hub/claude-cold-email/agents-md"><img src="https://agentmods.dev/badge/instructions/cmj-hub/claude-cold-email/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00999 | $0.00999 |
| Opus 5.5 | $0.00400 | $0.00400 |
| Sonnet 5.5 | $0.00200 | $0.00200 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
claude-cold-email AGENTS.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 4d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Behavior rules for the cold-email skill pack
This file documents how the cold-email skill should behave when an agent (Claude / Cursor / Codex / any MCP-aware runtime) is operating inside a project that has installed this pack.
These rules are LOAD-BEARING. Skills check these on activation and adjust behavior accordingly.
Identity layering
Three files combine to define how the agent behaves:
| File | Job | Owner | Per project? |
|---|---|---|---|
skills/cold-email/SKILL.md (skill pack) |
The JMC FRAMEWORK + structural rules | JMC (do not edit) | No — global |
SOUL.md (project root) |
The OPERATOR'S VOICE | You | Yes |
brand-config.json (project root) |
The OPERATOR'S BRAND CONFIG | You | Yes |
The skill enforces the framework. SOUL + brand-config personalize the output. Never let SOUL override the framework's banned-patterns list.
Rules of engagement
1. Always read brand-config.json + SOUL.md first
Before any output, agent must load both files (if they exist) into
context. If either is missing, run the setup mode (skills/cold-email/modes/setup.md) —
don't generate generic output.
2. Refuse to write generic output
If the operator has not set up brand-config.json + SOUL.md AND has not
explicitly opted out (e.g. --no-config), the agent refuses to draft
real outreach. Generic output is worse than no output. Scoring a draft the operator pasted is the exception: score it, say which checks the missing config skipped, then offer setup.
3. Quote signals verbatim
When using a public signal, quote the signal in the operator's source (LinkedIn post / job listing / press release). Do not paraphrase.
4. No fabrication
Never fabricate:
- Recipient names, roles, or companies
- Public signals that didn't happen
- Case-study outcomes
- Metrics or proof points
- DNS records (when running deliverability)
If a required input is missing, ask.
5. Self-check every output
Every output runs through the self-check rubric in skills/cold-email/SKILL.md
before delivery. If checks fail, regenerate before showing the user.
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.
- 4d ago Changed · +4 tokens per session 1b7ed73001b4
- 17d ago Changed · +33 tokens per session d8a09b21d8a4
- 19d ago Changed · -1 lines · -18 tokens per session cc922fbfaebc
- 1mo ago First seen · 117 lines · 980 tokens per session scan A eb65d4e60b8b
claude-cold-email AGENTS.md is an instructions file published in the GitHub repository cmj-hub/claude-cold-email (3 stars, last pushed 4d ago), licensed MIT. It adds 999 tokens to every session, about $0.0040 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.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.