Agent skill

Agent Severance

by mohitagw15856 in mohitagw15856/pm-claude-skills

Offboard an AI agent the way you'd offboard an employee — inventory what it knew and touched, export then purge its memory, revoke every credential and access grant, and write the handover for its…

MITAuto-check passed

Install Agent Severance

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill agent-severance -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills agent-severance --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agent-severance .claude/skills/agent-severance && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-severance
GitHub stars
1.4k
Token cost
~1.4k tokens
SKILL.md length
652 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Offboard an AI agent the way you'd offboard an employee — inventory what it knew and touched, export then purge its memory, revoke every credential and access grant, and write the handover for its…

  • Works in 5 steps: Inventory before touching anything… → Decide memory disposition per store, not… → Revoke with verification. Every row… → …
  • Decommissioning an agent
  • SKILL.md covers What This Skill Produces, Required Inputs, Process and Output Format, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Agent Severance is an agent skill from mohitagw15856/pm-claude-skills. Offboard an AI agent the way you'd offboard an employee — inventory what it knew and touched, export then purge its memory, revoke every credential and access grant, and write the handover for its successor (human or agent). Use when decommissioning an agent or bot, switching agent vendors, ending an AI pilot, or when someone asks 'what did this thing have access to?'. Produces a severance checklist, an access-revocation table, a memory disposition record, and a successor handover.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Decommissioning an agent
  • Switching agent vendors
  • Ending an AI pilot
  • Someone asks what did this thing have access to?

Example prompts

  • “what did this thing have access to?”
  • “/agent-severance”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Inventory before touching anything (unless incident — then revoke
  2. Decide memory disposition per store, not wholesale. Export what has
  3. Revoke with verification. Every row gets: the credential, who revokes
  4. Write the honest handover. What it was supposed to do, what it actually
  5. Announce the death. One message to the channels it served: it's gone,

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Severance loads about 1.4k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 652 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~126
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 652 words, ~1,429 tokens.

Download SKILL.mdSave it as .claude/skills/agent-severance/SKILL.md (or your agent's skills folder).
name
agent-severance
description
Offboard an AI agent the way you'd offboard an employee — inventory what it knew and touched, export then purge its memory, revoke every credential and access grant, and write the handover for its successor (human or agent). Use when decommissioning an agent or bot, switching agent vendors, ending an AI pilot, or when someone asks 'what did this thing have access to?'. Produces a severance checklist, an access-revocation table, a memory disposition record, and a successor handover.

Agent Severance Skill

Orgs learned employee offboarding the hard way: the contractor whose VPN worked for a year after the contract, the shared password nobody rotated. Long-lived agents recreate every one of those failure modes with worse logging — an agent accumulates credentials, memory, integrations, scheduled jobs, and undocumented responsibilities, and then one day it's "turned off" by deleting a chat window while its API keys live on. This skill runs the severance properly: know what it had, keep what's valuable, kill what's live, and hand over what it did.

What This Skill Produces

  • An inventory: everything the agent could touch (credentials, tools, data stores, channels), everything it knew (memory, context files, fine-tuning or instructions), and everything it did on a schedule
  • An access-revocation table with owner and verification step per row — revoked isn't revoked until someone confirmed the key is dead
  • A memory disposition record: exported / retained (where, why, how long) / purged (how verified) — the part compliance will ask about in 2027
  • A successor handover: the agent's actual duties, including the undocumented ones users discovered, for whoever inherits them

Required Inputs

Ask for (if not already provided):

  • The agent: platform, what it was for, how long it ran, who owned it
  • Known integrations and credentials (then treat the list as incomplete on principle — the inventory step hunts for the rest)
  • Why it's being offboarded (vendor switch, pilot ended, incident, cost) — incident-driven severance changes the order: revoke first, inventory second
  • What must survive: memory worth exporting, workflows someone still needs

Process

  1. Inventory before touching anything (unless incident — then revoke first). Hunt beyond the known list: API keys and OAuth grants · service accounts · webhook URLs pointing at it · scheduled/cron jobs it ran · channels it posted in · data stores it read or wrote · other agents that called it (the A2A dependencies nobody documented) · what its memory contains, including personal data.
  2. Decide memory disposition per store, not wholesale. Export what has value (decisions log, learned context) to an owned location; name a retention owner and period for anything kept; purge the rest and record how purged (vendor deletion request ≠ deleted — note what the vendor actually promises). Personal data follows your privacy policy's deletion rules, flagged explicitly.
  3. Revoke with verification. Every row gets: the credential, who revokes it, and the test that proves it's dead (the call that now fails). Rotate any shared secrets the agent ever held — its copy dying doesn't kill the copies.
  4. Write the honest handover. What it was supposed to do, what it actually did (ask its users — there are always undocumented duties), open threads mid-flight, and the workflows that will silently break next Tuesday when it stops.
  5. Announce the death. One message to the channels it served: it's gone, here's who/what replaces it, here's where its exported memory lives.
Show full SKILL.md (188 more words)Show less

Output Format

## Severance summary
[Agent, tenure, reason, severance owner, target date]

## Inventory
Access: [table — system, grant, discovered-how] · Knowledge: [stores + contents]
Duties: [scheduled + reactive + undocumented] · Dependents: [who/what calls it]

## Memory disposition
| Store | Export → where | Retain (owner, period) | Purge (method, verified how) |

## Revocation
| Credential/grant | Revoked by | Dead-key test | Status |

## Handover to successor
[Duties with enough detail to actually run them · open threads · will-break list]

## Announcement
[The message to its channels]

Quality Checks

  • The inventory includes at least one category the user didn't mention — scheduled jobs and agent-to-agent callers are the usual blind spots
  • Every revocation row has a verification test, not just an action
  • Shared secrets the agent held are rotated, not just revoked
  • Memory disposition distinguishes vendor-promised deletion from verified deletion, and flags personal data
  • The handover names what breaks when the agent stops — if the answer is "nothing", the duties inventory probably isn't done

Anti-Patterns

  • Do not equate "deleted the chat/app" with offboarded — the checklist exists because credentials outlive interfaces
  • Do not purge memory before the export decision — severance is irreversible in exactly one direction
  • Do not skip the users interview; the undocumented duties are the ones that page someone at 2am after shutdown
  • Do not write this as a vendor grudge document — it's an operational record compliance and the successor will both read

[[agent-hiring-panel]] is the front door this is the back door of; [[context-bankruptcy]] when the agent stays but its memory shouldn't; [[agent-incident-postmortem]] if an incident triggered this.

Example Trigger Phrases

  • "Decommissioning an agent."
  • "Switch agent vendors."
  • "Ending an AI pilot."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/agent-severance of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Agent Severance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Severance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Severance this skillmohitagw15856/pm-claude-skills1.4k—~1.4kAutomated safety check: PassMIT
Offboarding Exitsickn33/agentic-awesome-skills47k1 repos~3.8kAutomated safety check: PassMIT
Asset Inventorysickn33/agentic-awesome-skills47k2 repos~3.4kAutomated safety check: PassMIT
Relsa Severity AssessmentK-Dense-AI/scientific-agent-skills48k1 repos~5.2kAutomated safety check: NotesMIT
Zoho Inventory AutomationComposioHQ/awesome-claude-skills77k3 repos~757Automated safety check: PassNone
Odoo Inventory Optimizersickn33/agentic-awesome-skills47k2 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Offboarding Exit

    sickn33/agentic-awesome-skills

    Offboarding register: exit type, employee and manager, notice and final day, reason, handover owner, and done flags for knowledge transfer, assets, access and settlement.

    47k GitHub starsUsed in 1 repo~3.8k tokens
    Auto-check passed
  • Asset Inventory

    sickn33/agentic-awesome-skills

    Maintain IT asset inventory and configuration management database.

    47k GitHub starsUsed in 2 repos~3.4k tokens
    Auto-check passed
  • Relsa Severity Assessment

    K-Dense-AI/scientific-agent-skills

    Supports multivariate severity assessment and exploratory endpoint-time score forecasting for laboratory animal studies using the RELSA (RELative Severity Assessment) score and ARIMA-based foRcast…

    48k GitHub starsUsed in 1 repo~5.2k tokens
    Data & AnalyticsAuto-check: notes
  • Zoho Inventory Automation

    ComposioHQ/awesome-claude-skills

    Automate Zoho Inventory tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~757 tokens
    Productivity & AutomationAuto-check passed
  • Odoo Inventory Optimizer

    sickn33/agentic-awesome-skills

    Expert guide for Odoo Inventory: stock valuation (FIFO/AVCO), reordering rules, putaway strategies, routes, and multi-warehouse configuration.

    47k GitHub starsUsed in 2 repos~1.1k tokens
    Business, Finance & HRAuto-check passed
  • 为多地点零售商提供需求预测、安全库存优化、补货规划及促销提升估算的编码化专业知识。基于拥有15年以上管理数百个SKU经验的需求规划师的专业知识。包括预测方法选择、ABC/XYZ分析、季节性过渡管理及供应商谈判框架。适用于预测需求、设定安全库存、规划补货、管理促销或优化库存水平时使用。

    276k GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about Agent Severance

What does Agent Severance do?

Offboard an AI agent the way you'd offboard an employee — inventory what it knew and touched, export then purge its memory, revoke every credential and access grant, and write the handover for its…. Agent Severance is an agent skill from mohitagw15856/pm-claude-skills. Offboard an AI agent the way you'd offboard an employee — inventory what it knew and touched, export then purge its memory, revoke every credential and access grant, and write the handover for its successor (human or agent).

When should I use Agent Severance?

Agent Severance fits situations like: decommissioning an agent; switching agent vendors; ending an AI pilot; someone asks what did this thing have access to?.

How do I install Agent Severance in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill agent-severance -a claude-code`. Or copy the skill folder (skills/agent-severance in mohitagw15856/pm-claude-skills) into .claude/skills/agent-severance in your project. Claude Code loads it when a task matches its description.

How do I install Agent Severance in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill agent-severance -a codex`. Or copy the skill folder (skills/agent-severance in mohitagw15856/pm-claude-skills) into .agents/skills/agent-severance in your project. Codex loads it when a task matches its description.

Can I use Agent Severance in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill agent-severance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-severance, .gemini/skills/agent-severance, .github/skills/agent-severance and .opencode/skills/agent-severance in your project.

What does Agent Severance need to run?

SKILL.md names no scripts, command-line tools or credentials: Agent Severance is instructions for the agent only.

Does Agent Severance access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agent Severance safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agent Severance use?

Agent Severance is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Severance use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agent Severance?

Skills that share tags, products or a category with Agent Severance: Offboarding Exit (sickn33/agentic-awesome-skills, 47k stars), Asset Inventory (sickn33/agentic-awesome-skills, 47k stars), Relsa Severity Assessment (K-Dense-AI/scientific-agent-skills, 48k stars) and Zoho Inventory Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Severance?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.