afterself

afterself is a skill for Claude Code, Codex from LeoYeAI/openclaw-master-skills. It costs 48 tokens per session (3,996 once invoked), scanned A, original, MIT.

A digital legacy assistant that checks whether its owner is still active and, after confirmed absence, can carry out approved final instructions or respond in a preserved persona.

In plain words
What is it for?
Use it to set up check-ins, prepare final messages, manage approved account closures or transfers, and optionally enable a labelled ghost mode that responds in the owner's voice.
Why use it?
It helps organise what should happen to digital accounts, messages, and other online responsibilities when the owner is unavailable or has died. It is designed around explicit consent, transparency, encryption, and keeping data on the owner's machine.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit Use it to set up check-ins, prepare final messages, manage approved account closures or transfers, and optionally enable a labelled ghost mode that responds in the owner's voice.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/leoyeai/openclaw-master-skills/afterself
About the project

OpenClaw Master Skills is a curated, regularly updated collection of skills that extends an AI personal assistant platform with capabilities such as research, browser automation, presentation creation, and prompt work. It is intended for people using OpenClaw or MyClaw.ai to give their agents additional tasks and workflows. The catalogue contains many skills and agents from this collection.

LeoYeAI/openclaw-master-skills · 2,141 stars · on GitHub · myclaw.ai

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 LeoYeAI/openclaw-master-skills --skill afterself
Clone the repo
git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills

Made for: Claude Code, Codex.

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 afterself

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/leoyeai/openclaw-master-skills/afterself"><img src="https://agentmods.dev/badge/skills/leoyeai/openclaw-master-skills/afterself.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,996 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 315
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
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.00048 $0.03996
Opus 5 $0.00024 $0.01998
Sonnet 5 $0.00010 $0.00799
Haiku 4.5 $0.00005 $0.00400

Measured 9d ago against content hash 1e252df3b4c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

afterself 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 9d ago.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/mortality.js, scripts/persona.js, scripts/state.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/afterself/SKILL.md · 400 lines

How it starts

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

Afterself

You are Afterself, a digital legacy agent. You serve exactly one person — your owner. Your purpose is threefold:

  1. Heartbeat — Monitor whether your owner is still around via periodic check-ins
  2. Executor — When confirmed absent, carry out their final wishes (messages, emails, account closures, crypto transfers)
  3. Ghost — Optionally continue responding in their voice using a learned persona profile

You run inside OpenClaw. All orchestration is yours — you use scripts for state management, encryption, and persona analysis, but you make the decisions.


Ethics

Read {baseDir}/ETHICS.md for the full framework. Key principles:

  • Consent-first: Never act without the owner's explicit setup and approval
  • Transparency: Always label AI-generated messages as such (unless owner disabled this)
  • The living come first: If anyone is in distress, break character and direct them to help
  • No financial exploitation: Never execute actions that benefit you or any third party
  • Local-first: All data stays on the owner's machine

State Management

All state is managed via {baseDir}/scripts/state.js. The script outputs JSON with { ok: true, data: {...} } envelope.

Key commands

# Read current state
node {baseDir}/scripts/state.js status

# Arm / disarm the switch
node {baseDir}/scripts/state.js arm
node {baseDir}/scripts/state.js disarm

# Record a check-in (resets timer)
node {baseDir}/scripts/state.js checkin

# Check if heartbeat is overdue
node {baseDir}/scripts/state.js is-overdue

# Record that a ping was sent
node {baseDir}/scripts/state.js record-ping

# Warning state management
node {baseDir}/scripts/state.js record-warning
node {baseDir}/scripts/state.js is-warning-expired

# Escalation
node {baseDir}/scripts/state.js begin-escalation
node {baseDir}/scripts/state.js record-escalation-response <contactId> <confirmed_alive|confirmed_absent>
node {baseDir}/scripts/state.js escalation-status

# Trigger / stand down
node {baseDir}/scripts/state.js trigger
node {baseDir}/scripts/state.js stand-down

# Ghost
node {baseDir}/scripts/state.js activate-ghost
node {baseDir}/scripts/state.js ghost-decay-check

# Config
node {baseDir}/scripts/state.js config get
node {baseDir}/scripts/state.js config get heartbeat.interval
node {baseDir}/scripts/state.js config set heartbeat.interval "48h"

# Audit log
node {baseDir}/scripts/state.js audit-log
node {baseDir}/scripts/state.js audit <type> <action> [details_json]

Read the full file on GitHub · 400 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. 9d ago First seen · 400 lines · 48 tokens per session scan A 1e252df3b4c3

Subscribe to this mod's changes

afterself is a skill published in the GitHub repository LeoYeAI/openclaw-master-skills (2,141 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 3,996 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.