agentmods.dev

lifecycle-copy

lifecycle-copy is a skill for Claude Code from ali-demirbas/claude-lifecycle. It costs 77 tokens per session (2,351 once invoked), scanned A, original, MIT.

A rule-checked writing workflow for customer messages sent by email, push notification, SMS, in-app message, or WhatsApp. It creates variants and character counts while applying brand, channel, and compliance rules.

In plain words
What is it for?
Use it to write send-ready messages for steps in a customer journey. It requires either a journey document or a description containing the channel and purpose.
Why use it?
It helps prevent messages from exceeding channel limits or using banned words and missing required consent text. It also ensures the copy is reviewed before delivery.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-lifecycle plugin — 11 skills, 4 agents, 1 hook shipped together

not rated 2repo 20d ago A scan 77 tokens original MIT

Good fit Use it to write send-ready messages for steps in a customer journey. It requires either a journey document or a description containing the channel and purpose.

Compare 6 skills from other repositories ↓
View source ↗ ali-demirbas/claude-lifecycle ali-demirbas.github.io
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ali-demirbas/claude-lifecycle
Claude Code
/plugin install claude-lifecycle

Made for: Claude Code.

Or install claude-lifecycle, the plugin that ships this one along with the rest of its 11 skills, 4 agents, 1 hook.

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 lifecycle-copy

README.md
[![agentmods](https://agentmods.dev/badge/skills/ali-demirbas/claude-lifecycle/lifecycle-copy.svg)](https://agentmods.dev/skills/ali-demirbas/claude-lifecycle/lifecycle-copy)
Your own site
<a href="https://agentmods.dev/skills/ali-demirbas/claude-lifecycle/lifecycle-copy"><img src="https://agentmods.dev/badge/skills/ali-demirbas/claude-lifecycle/lifecycle-copy.svg" alt="Measured on agentmods" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,351 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 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.00077 $0.02351
Opus 5 $0.00039 $0.01175
Sonnet 5 $0.00015 $0.00470
Haiku 4.5 $0.00008 $0.00235

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

Security

Grade A, and why

lifecycle-copy 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 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.

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.

skills/lifecycle-copy/SKILL.md · 94 lines

How it starts

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

Lifecycle Copy — Channel Copywriting

Produce send-ready copy for journey steps. Copy here is an engineering artifact: it has hard constraints (limits, banned words, consent text) and is reviewed before it is shown. The mandatory format is ${CLAUDE_PLUGIN_ROOT}/templates/copy-output.md.

When NOT to use this

  • No journey doc or step description exists yet — there's nothing to write copy for; run lifecycle-journeys first or supply a step description (channel + intent) directly.
  • The ask is whether EXISTING, already-shipped copy complies with channel/lexicon rules — that's lifecycle-audit's dimension 7 (spot-check), not this skill; this skill's review loop only covers copy it itself writes.
  • The need is a CRM-agnostic structured export of copy already written — that's lifecycle-export, not this skill.

Inputs (gate)

  1. A journey doc (from lifecycle-journeys) OR a user-supplied step description (channel + intent minimum).
  2. The rule chain, loaded in inheritance order (CLAUDE.md rule 8 — most specific wins, bans/compliance strictest wins):
    • ${CLAUDE_PLUGIN_ROOT}/knowledge/brands/<brand>.md if it exists — tone/formality override; extra_banned_words extend all ban lists; brand_vocabulary is authoritative for product/feature names.
    • ${CLAUDE_PLUGIN_ROOT}/knowledge/lexicons/locales/<lang>.md per target language — voice, emotion calibration, market red lines.
    • ${CLAUDE_PLUGIN_ROOT}/knowledge/lexicons/<sector>.md. No lexicon for the sector → use the closest and say so.
  3. Tone + formality + language(s) from the brand file or Intake Summary. Missing → trigger lifecycle-intake (tone questions only).
  4. Persona context: the journey doc's §3 audience definition (segment, lifecycle stage, RFM tier where known) is passed to the writer — copy addresses that persona, never a generic user.
  5. Failed-strategies check: if output/<brand>/failed-strategies.md exists, a logged powered failure is not re-proposed to the same segment; when a strategy is skipped because of the log, say which entry caused it.
  6. Winning-strategies check: if output/<brand>/winning-strategies.md exists and has a confirmed entry for this segment/journey stage, pass it to the writer as a precedent — it informs one variant's starting angle, never both; the other variant still explores a genuinely different, less-tested angle. A precedent narrows a starting point, it doesn't replace the two-distinct-angles rule.

Read the full file on GitHub · 94 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. 7d ago First seen · 94 lines · 77 tokens per session scan A c93e8667d6fc

Subscribe to this mod's changes

lifecycle-copy is a skill published in the GitHub repository ali-demirbas/claude-lifecycle (2 stars, last pushed 20d ago), licensed MIT. It adds 77 tokens to every session and 2,351 once invoked, about $0.0004 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-31.

Claude CodeMarketing and SEOWriting and docsclaude-code-plugincrmcustomer-journeyga4growth-marketing
Related

Other skills, from other repositories

geo-optimization

Use when the user wants to improve their AI visibility (GEO score) across ChatGPT, Gemini, Perplexity, Claude, Grok, DeepSeek, Meta AI, and Copilot. Covers the full optimization playbook, what each sub-score rewards, fix prioritization, and discovery stack requirements.

studiomeyer-io/studiomeyer-marketplace · 66 tokens

crm-workflow

Use when the user is working with StudioMeyer CRM and you need to pick the right tool. Covers the Lead → Contact → Deal → Pipeline flow, daily CRM routine, and how to run import/export safely.

studiomeyer-io/studiomeyer-marketplace · 47 tokens

memory-import-guide

Use when the user wants to import conversation history from ChatGPT, Claude, Gemini, Microsoft Copilot, or Perplexity into StudioMeyer Memory. Covers export steps per platform, file formats, and how to run the import safely.

studiomeyer-io/studiomeyer-marketplace · 52 tokens

memory-workflow

Use when the user is working with StudioMeyer Memory and you need to pick the right tool. Covers when to use search vs entity tools vs learn vs decide, how to structure queries, and how to avoid duplicate writes.

studiomeyer-io/studiomeyer-marketplace · 49 tokens

persona-usage

Use when the user wants to pick the right Crew persona for a task, combine multiple personas, or understand how personas differ. Covers when to activate which role, how workflows chain them, and how to avoid persona misuse.

studiomeyer-io/studiomeyer-marketplace · 48 tokens

add-vacancy

Use whenever the user wants to ingest one or more job vacancies into Job Search HQ. Triggers: /add-vacancy, "add this vacancy", "add these jobs", pasting one or more job URLs, or pasting an aggregator/search URL and asking to expand it. Handles a single URL, a bulk list, or an aggregator page (DOU / Djinni /…

Miracle-Aligner/job-search-hq · 143 tokens