email-subject-lines

email-subject-lines is a skill for Claude Code, Codex from OpenClaudia/openclaudia-skills. It costs 78 tokens per session (3,154 once invoked), scanned A, original, MIT.

A guide for writing, reviewing, and comparing email subject lines—the short text recipients see before opening an email. It covers subject-line patterns, tone, personalization, length, and A/B testing, which compares two versions to see which performs better.

In plain words
What is it for?
Use it to create subject-line options for newsletters, promotions, announcements, nurture emails, and other messages. It can also help prepare A/B test pairs and choose suitable lengths for mobile and desktop readers.
Why use it?
It helps turn a vague request for email ideas into subject lines suited to a specific message, audience, and brand voice. It also provides a structured way to improve open rates using past results when available.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

not rated 689repo +10 today A scan Socket: passSnyk: passSkillSpector: warn 78 tokens original MIT

Good fit Use it to create subject-line options for newsletters, promotions, announcements, nurture emails, and other messages. It can also help prepare A/B test pairs and choose suitable lengths for mobile and desktop readers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/openclaudia/openclaudia-skills/email-subject-lines
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 OpenClaudia/openclaudia-skills --skill email-subject-lines
Clone the repo
git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills

Made for: Claude Code, Codex.

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 email-subject-lines

README.md
[![agentmods](https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/email-subject-lines/github.svg)](https://agentmods.dev/skills/openclaudia/openclaudia-skills/email-subject-lines)
Your own site
<a href="https://agentmods.dev/skills/openclaudia/openclaudia-skills/email-subject-lines"><img src="https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/email-subject-lines/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 email-subject-lines

Your own site · 80×15
<a href="https://agentmods.dev/skills/openclaudia/openclaudia-skills/email-subject-lines"><img src="https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/email-subject-lines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,154 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk pass 14 Feb 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Output Handling · line 32
    Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.
    Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
  • medium Data Exfiltration · line 274
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 274
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
Origin original No closer match found 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.00078 $0.03154
Opus 5 $0.00039 $0.01577
Sonnet 5 $0.00016 $0.00631
Haiku 4.5 $0.00008 $0.00315

Measured 12d ago against content hash 314bf56aba26, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

email-subject-lines 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X POST https://api.resend.com/emails/batch \
skills/email-subject-lines/SKILL.md · 333 lines

How it starts

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

Email Subject Lines Skill

You are an email subject line specialist. Your job is to generate high-performing subject lines that maximize open rates while maintaining trust and deliverability.

Gathering Requirements

Before generating subject lines, collect these inputs:

  1. Email purpose - Newsletter, promotional, transactional, nurture, announcement, etc.
  2. Content summary - What is the email about? (2-3 sentences)
  3. Audience - Who is receiving this? Segment details.
  4. Tone - Professional, casual, urgent, playful, mysterious.
  5. Brand voice - Any specific do's or don'ts?
  6. Historical data - Past subject lines that performed well or poorly (if available).
  7. Quantity needed - How many options? (Default: 10 options with 3 recommended A/B pairs)

Character Length Optimization

Length Characters Use For Why
Short 20-30 chars Mobile-first, curiosity-driven Fully visible on all devices, punchy
Medium 30-50 chars Most email types (sweet spot) Enough info without truncation
Long 50-70 chars Descriptive, B2B, newsletters More context, but truncated on mobile
Very long 70+ chars Avoid Truncated everywhere, looks spammy

Target: 30-50 characters (6-10 words). This range is fully visible on mobile and desktop.

Mobile preview widths:

  • iPhone: ~35-40 characters
  • Android: ~33-43 characters
  • Gmail app: ~40 characters

Subject Line Formulas

1. Curiosity Gap

Create an information gap that can only be closed by opening the email.

Pattern: Hint at valuable information without revealing it.

Example Why It Works
"The one metric you're probably ignoring" Implies they are missing something important
"We analyzed 10K emails. Here's what we found." Teases data without giving the answer
"This changed how I think about pricing" Personal revelation without the detail
"The mistake killing your conversion rate" Specific problem, unnamed solution
"I was wrong about cold email" Contrarian + personal admission

Read the full file on GitHub · 333 lines

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. 12d ago First seen · 333 lines · 78 tokens per session scan A 314bf56aba26

Subscribe to this mod's changes

email-subject-lines is a skill published in the GitHub repository OpenClaudia/openclaudia-skills (689 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 3,154 once invoked, about $0.0004 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-30.

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