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 skills add tomzx/agents --skill sunset-productgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/sunset-product)<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.
<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>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.00037 | $0.00475 |
| Opus 5 | $0.00018 | $0.00237 |
| Sonnet 5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
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 6d 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.
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
sunsetgate verdict, or a manual decision to retire, withhealth-report.mdandfeedback-loop.mdas evidence.
Steps
- 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.
- Identify affected users and data: who depends on this, and what must be migrated or preserved.
- Define the migration path: where users go, what data exports exist, and the effort required.
- Build the communication timeline: advance notice, deprecation notice, and final cutover date. State the notice period (give users enough runway).
- Define the ramp-down: feature flags, access controls, and the order in which capabilities are removed.
- Capture the learning via
run-retrospectiveso the sunset compounds knowledge. - Write
eol-plan.mdto 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.
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.
- 6d ago First seen · 46 lines · 37 tokens per session scan A f9e0fcbc22a7
sunset-product is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 475 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.