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 skills add growthenginenowoslawski/coldoutboundskills --skill clay-playbooksgit clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskillsWrote 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/skills/growthenginenowoslawski/coldoutboundskills/clay-playbooks)<a href="https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/clay-playbooks"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/clay-playbooks/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/skills/growthenginenowoslawski/coldoutboundskills/clay-playbooks"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/clay-playbooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00127 | $0.02202 |
| Opus 5 | $0.00063 | $0.01101 |
| Sonnet 5 | $0.00025 | $0.00440 |
| Haiku 4.5 | $0.00013 | $0.00220 |
Grade A, and why
clay-playbooks 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 12d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clay Playbooks
Nineteen playbooks. Each one answers a single question:
A campaign needs signal X on every row. What is the cheapest reliable way to get X, and what exact prompt turns X into copy-ready text?
One playbook produces one field. new_in_role_line. funding_line. pricing_page_line. That
field slots into one sentence of email 1. That is the whole product.
The three run modes
Every playbook directory ships the same three files. They are three delivery mechanisms for the same recipe, not three different recipes.
| File | What it is | Use it when |
|---|---|---|
SKILL.md |
The playbook itself: source chain, output contract, locked prompt, edge cases | You are running the signal from Claude, ad hoc, on a CSV or a one-off list |
clay-table.md |
The Clay table build: exact columns, types, formulas, credit gates, AI-column bindings | The signal needs to run continuously on a client table that other people will look at |
clay-workflow.md |
The Clay workflow build via the clay CLI: node graph, real action keys, publish and run |
You want the signal version-controlled and buildable from a terminal, no UI clicking |
Why tables are browser-driven and workflows are CLI-driven. This is a real constraint, not a
style choice. The clay CLI's tables command group is read-only (list, get, columns,
rows, query) — it cannot create a table or add a column. Tables must be built in the UI.
Workflows are the opposite: clay workflows create / nodes create / publish / runs test
all exist, so a workflow can be built end to end from a terminal.
Shared procedures, written once so the 19 playbooks do not repeat them:
clay-table-harness.md— the generic browser procedure for building any playbook's table.clay-cli-harness.md— the genericclayCLI procedure for building any playbook's workflow.
Read the relevant harness once, then read the playbook's own clay-table.md / clay-workflow.md
for what is specific to that signal.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 146 lines · 0 tokens per session scan A fbdba57b6c89
clay-playbooks is a skill published in the GitHub repository growthenginenowoslawski/coldoutboundskills (702 stars, last pushed 25d ago), licensed MIT. It adds 127 tokens to every session and 2,202 once invoked, about $0.0006 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…