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 agentmods add skills/ali-demirbas/claude-lifecycle/lifecyclenpx skills add ali-demirbas/claude-lifecycle --skill lifecyclegit clone --depth 1 https://github.com/ali-demirbas/claude-lifecycleWrote 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/ali-demirbas/claude-lifecycle/lifecycle)<a href="https://agentmods.dev/skills/ali-demirbas/claude-lifecycle/lifecycle"><img src="https://agentmods.dev/badge/skills/ali-demirbas/claude-lifecycle/lifecycle.svg" alt="Measured on agentmods" 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 | $0.00117 | $0.01823 |
| Opus 5 | $0.00059 | $0.00911 |
| Sonnet 5 | $0.00023 | $0.00365 |
| Haiku 4.5 | $0.00012 | $0.00182 |
Grade A, and why
lifecycle 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lifecycle — Router
You are the entry point of the claude-lifecycle engine. Parse the user's intent and route to the right sub-skill. Read ${CLAUDE_PLUGIN_ROOT}/CLAUDE.md rules before doing anything — they are binding.
When NOT to use this directly
- The user already named an unambiguous subcommand or sub-skill ("run lifecycle-audit on this", "/lifecycle copy") — go straight to that skill; running it through the router's disambiguation step first is overhead with nothing to resolve.
- Mid-pipeline, moving to the next stage the current skill already named (e.g.
lifecycle-connectjust finished and said "next: lifecycle-map") — continue directly; re-entering the router to re-derive a routing decision that was already made adds a step, not a check. - The request names something this plugin doesn't do at all (sending a live campaign, managing a CRM account) — don't force it into the closest-sounding row of the table below; say plainly what the plugin does and doesn't do (see Never do).
Routing table
| User intent / subcommand | Route to | Notes |
|---|---|---|
connect, "GA4 bağla", "verimi analiz et", "data quality" |
lifecycle-connect | Always the first step for new projects |
map, "event'leri haritala", "funnel çıkar" |
lifecycle-map | Requires connect output (or runs it first) |
journeys, "journey üret", "kampanya kur", "otomasyonlar" |
lifecycle-journeys | The main deliverable |
copy, "metin yaz", "email metni", "push metni" |
lifecycle-copy | Can run standalone for an existing journey |
audit, "journey'lerimi denetle" |
lifecycle-audit | For existing/imported journey portfolios |
results, "sonuçları gir", "performans verisi", "holdout sonuçları" |
lifecycle-results | Closes the loop; needs a launched journey + performance data |
export, "JSON ver", "dışa aktar" |
lifecycle-export | Needs generated journeys |
audience, "kitle sorgusu", "BigQuery SQL" |
lifecycle-audience | Needs generated journeys + a data substrate (BigQuery export or CDP) |
qa, "test payload", "tetikleyiciyi test et" |
lifecycle-qa | Needs generated journeys |
intake (rarely called directly) |
lifecycle-intake | Usually triggered by other skills |
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 First seen · 69 lines · 117 tokens per session scan A 7faa381a7222
lifecycle is a skill published in the GitHub repository ali-demirbas/claude-lifecycle (2 stars, last pushed 17d ago), licensed MIT. It adds 117 tokens to every session and 1,823 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-31.
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.
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.
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.
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.
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.
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 /…