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/lifecycle-exportnpx skills add ali-demirbas/claude-lifecycle --skill lifecycle-exportgit 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-export)<a href="https://agentmods.dev/skills/ali-demirbas/claude-lifecycle/lifecycle-export"><img src="https://agentmods.dev/badge/skills/ali-demirbas/claude-lifecycle/lifecycle-export.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.1 | $0.00055 | $0.01103 |
| Opus 5 | $0.00028 | $0.00551 |
| Sonnet 5 | $0.00011 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
lifecycle-export 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 5d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lifecycle Export — Structured Output
Convert generated journey docs into machine-consumable formats. Exports are derived from journey docs — never hand-author an export that diverges from its doc.
When NOT to use this
- No journeys exist yet — there's nothing to convert; run
lifecycle-journeysfirst. - The ask is just the normal user-facing deliverable for a fresh run — the HTML canvas is already produced by
lifecycle-journeys/lifecycle-copy's own Output steps; this skill is for the additional formats (JSON, Mermaid, CSV, the standalone report) or a re-export on request, not the default path. - Copy hasn't finished its review loop yet — export refuses to ship unreviewed copy regardless; the fix is finishing
lifecycle-copy's write → review → fix cycle, not forcing an export around it.
Formats
| Format | What | Notes |
|---|---|---|
| HTML canvas (THE default deliverable — user-approved format) | Journey tabs + meta card (SEGMENT/AMAÇ/PRIMARY METRIC) + vertical tree canvas: entry/decision/message/exit node cards, Evet/Hayır branch pills, SVG connectors, tooltips, DETAYLAR toggles, print view, HTML/PDF download hints | Reproduce ${CLAUDE_PLUGIN_ROOT}/templates/canvas.html EXACTLY — replace only the JOURNEYS data array, eyebrow/h1/lede texts, and HOLDOUT_TIP/DATA_NOTE constants with real data. Never redesign it, never add extra views |
| HTML report (optional, on request) | Single page: DQS breakdown, urgent findings, portfolio table, roadmap | ${CLAUDE_PLUGIN_ROOT}/templates/report.html — offer only when the user asks for an assessment summary beyond the canvas |
| JSON | One file per journey, validating against ${CLAUDE_PLUGIN_ROOT}/templates/journey.schema.json |
The canonical machine export. Waits use ISO 8601 durations (PT1H, P1D) |
| Mermaid | flowchart TD per journey (already in each doc §8) |
Bundled into one .md on request |
| CSV | Flat step list: journey_id, step, wait, channel, intent, branch_condition | For spreadsheet review with non-technical stakeholders |
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.
- 5d ago First seen · 45 lines · 55 tokens per session scan A 74b810741e24
lifecycle-export is a skill published in the GitHub repository ali-demirbas/claude-lifecycle (2 stars, last pushed 18d ago), licensed MIT. It adds 55 tokens to every session and 1,103 once invoked, about $0.0003 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.
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.
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-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 /…