personalization-subagent-pattern

personalization-subagent-pattern is a skill for Claude Code from AlexisMarasigan/coldoutboundskills. It costs 106 tokens per session (2,673 once invoked), scanned A, a copy of personalization-subagent-pattern, MIT.

A review-and-approval process for generating personalized cold-email text for many leads using parallel Claude Code Task sub-agents, which are separate workers handling parts of the list.

In plain words
What is it for?
Use it to personalize batches of up to hundreds of leads through sample reviews, feedback rounds, and larger parallel runs.
Why use it?
It lets you test and correct the personalization approach on a small sample before applying it to the full list, reducing repeated mistakes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; mentions Claude Code.

Part of the coldoutboundskills plugin — 28 skills shipped together

Good fit Use it to personalize batches of up to hundreds of leads through sample reviews, feedback rounds, and larger parallel runs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alexismarasigan/coldoutboundskills/personalization-subagent-pattern
Install

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.

Any agent
npx skills add AlexisMarasigan/coldoutboundskills --skill personalization-subagent-pattern
Clone the repo
git clone --depth 1 https://github.com/AlexisMarasigan/coldoutboundskills

Made for: Claude Code.

Or install coldoutboundskills, the plugin that ships this one along with the rest of its 28 skills.

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.

agentmods badge for personalization-subagent-pattern

README.md
[![agentmods](https://agentmods.dev/badge/skills/alexismarasigan/coldoutboundskills/personalization-subagent-pattern/github.svg)](https://agentmods.dev/skills/alexismarasigan/coldoutboundskills/personalization-subagent-pattern)
Your own site
<a href="https://agentmods.dev/skills/alexismarasigan/coldoutboundskills/personalization-subagent-pattern"><img src="https://agentmods.dev/badge/skills/alexismarasigan/coldoutboundskills/personalization-subagent-pattern/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.

agentmods 80×15 button for personalization-subagent-pattern

Your own site · 80×15
<a href="https://agentmods.dev/skills/alexismarasigan/coldoutboundskills/personalization-subagent-pattern"><img src="https://agentmods.dev/badge/skills/alexismarasigan/coldoutboundskills/personalization-subagent-pattern.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 106 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,673 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00106 $0.02673
Opus 5 $0.00053 $0.01337
Sonnet 5 $0.00021 $0.00535
Haiku 4.5 $0.00011 $0.00267

Measured 9d ago against content hash 0278a8a4a618, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

personalization-subagent-pattern 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 9d 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.

Origin

This is a copy

100% identical to personalization-subagent-pattern — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/personalization-subagent-pattern/SKILL.md · 276 lines

How it starts

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

Personalization Sub-Agent Pattern

Cold email personalization at scale requires per-lead generation. Claude Code's Task tool lets you fan out to many sub-agents in parallel, each personalizing a slice of the lead list. This skill defines the reusable approval-loop pattern.

Always Task tool — never an API key

This skill runs entirely inside Claude Code via the Task tool. No Anthropic SDK calls, no OpenAI calls. This is intentional:

  • No extra API spend. Uses your Claude Code plan.
  • No key management. Works out of the box.
  • Parallel by design. Claude Code spawns multiple Task sub-agents in one message, letting 100 leads finish in the time it takes to personalize 10.

At very large scale (1,000+ leads), the tuned prompt can optionally be shipped to the Anthropic API for throughput. But TUNING and normal campaign runs (under 500 leads) always go through the Task tool.

The approval loop (before full fan-out)

Don't personalize 500 leads and then discover the prompt is wrong. Loop first, then scale.

Round 0 — Sample on 1 lead

  1. Pick one lead from the batch with a rich company_description.
  2. Show the user: "Here's the company description I'm working with. Based on this, what would you say to personalize?"
  3. Display what YOU (Claude) would generate for situation_line, value_line, cta_soft.
  4. Ask: "Does this feel right? Edit it, and I'll re-tune."

Round 1-N — Batch of 10 with approval

  1. Spawn one Task sub-agent with the current prompt + 10 leads.
  2. Display all 10 results in a table:
    Lead                  | situation_line                          | value_line                    | cta_soft
    [email protected]         | You're building the only APM for Ruby.  | Our Ruby customers find ...   | Worth 10 min?
    [email protected]      | ...                                     | ...                           | ...
    
  3. Ask: "Any edits? Point at the row number and say what's wrong."
  4. If the user has edits, update the prompt (or add rules like "never use the word X") and re-run a new batch.
  5. If the user has zero edits for 2 consecutive rounds, the prompt is locked. Scale to the full list.

Read the full file on GitHub · 276 lines

Files

What ships with it

1 file 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.

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.

  1. 9d ago First seen · 276 lines · 106 tokens per session scan A 0278a8a4a618

Subscribe to this mod's changes

personalization-subagent-pattern is a skill published in the GitHub repository AlexisMarasigan/coldoutboundskills (4 stars, last pushed 4mo ago), licensed MIT. It adds 106 tokens to every session and 2,673 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to personalization-subagent-pattern, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens