sunset-product

sunset-product is a skill for Claude Code from tomzx/agents. It costs 37 tokens per session (478 once invoked), scanned A, original, MIT.

A workflow for retiring a product or feature in an orderly way. It covers moving users and data, communicating the change, and removing access over time.

In plain words
What is it for?
Use it to record the reason for retirement, identify affected users and data, define migration and communication plans, and schedule the shutdown steps.
Why use it?
It reduces the risk of breaking user commitments or losing data when a product no longer provides enough value to keep running.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to record the reason for retirement, identify affected users and data, define migration and communication plans, and schedule the shutdown steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tomzx/agents/sunset-product
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 tomzx/agents --skill sunset-product
Clone the repo
git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

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 sunset-product

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/tomzx/agents/sunset-product"><img src="https://agentmods.dev/badge/skills/tomzx/agents/sunset-product.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 478 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.00037 $0.00478
Opus 5.5 $0.00015 $0.00191
Sonnet 5.5 $0.00007 $0.00096
Haiku 4.5 $0.00004 $0.00048

Measured 22d ago against content hash 1900c32d5f41, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sunset-product 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 22d 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/pdlc/skills/sunset-product/SKILL.md · 50 lines

What it actually says

Sunset Product

End-of-life is a normal PDLC outcome, not an admission of failure. When the Measure gate returns sunset (or when a product becomes net-negative), this skill produces the plan to retire it responsibly: migrate users, communicate, and wind down without breaking promises.

Prerequisites

  • Apply the shared PDLC conventions in skills/pdlc/references/shared.md.
  • A sunset gate verdict, or a manual decision to retire, with health-report.md and feedback-loop.md as evidence.

Steps

  1. Confirm the sunset rationale and record it (the value is no longer there, the cost exceeds it, or it is being superseded). Reference the health/feedback evidence.
  2. Identify affected users and data: who depends on this, and what must be migrated or preserved.
  3. Define the migration path: where users go, what data exports exist, and the effort required.
  4. Build the communication timeline: advance notice, deprecation notice, and final cutover date. State the notice period (give users enough time).
  5. Define the ramp-down: feature flags, access controls, and the order in which capabilities are removed.
  6. Capture the learning via run-retrospective so the sunset adds to knowledge.
  7. Write eol-plan.md to the initiative directory.

Output Format

Use the template at skills/pdlc/templates/initiatives/eol-plan.md.

Outcome

If $OUTCOME_YAML is set, emit verdict: planned.

Completion Checklist

  • Rationale recorded and tied to evidence
  • Affected users and data identified
  • Migration path defined (or "no migration needed" justified)
  • Communication timeline with a stated notice period
  • Ramp-down order defined
  • Retrospective captured

Next Step

Run brief-stakeholders for the sunset comms, and kill-initiative to free the capacity. Sending any user-facing communication requires explicit confirmation.

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. 22d ago Changed · +4 lines 1900c32d5f41
  2. 24d ago Changed 9bfd6baa40e6
  3. 1mo ago First seen · 46 lines · 37 tokens per session scan A f9e0fcbc22a7

Subscribe to this mod's changes

sunset-product is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 478 once invoked, about $0.0001 per session on Opus 5.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-09-03.