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 agentproto/ts --skill ap-lifecyclegit clone --depth 1 https://github.com/agentproto/tsWrote 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/agentproto/ts/ap-lifecycle)<a href="https://agentmods.dev/skills/agentproto/ts/ap-lifecycle"><img src="https://agentmods.dev/badge/skills/agentproto/ts/ap-lifecycle/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/agentproto/ts/ap-lifecycle"><img src="https://agentmods.dev/badge/skills/agentproto/ts/ap-lifecycle.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.00077 | $0.01039 |
| Opus 5.5 | $0.00031 | $0.00416 |
| Sonnet 5.5 | $0.00015 | $0.00208 |
| Haiku 4.5 | $0.00008 | $0.00104 |
Grade A, and why
ap-lifecycle 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 1mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Lifecycle (Kill, Restart, Archive, GC)
When to use
You need to end, pause, recover, hide, or bulk-clean agentproto sessions — distinct from spawning (ap-spawn-agent) or waiting on them (ap-wait-fanin). Covers the full state machine: live → interrupted/killed → restarted, and live → archived/gc'd → gone from the default listing.
MCP: ending or pausing a turn
agent_kill terminates a session outright.
{ "tool": "agent_kill", "args": { "sessionId": "sess_abc123" } }
agent_interrupt cancels the in-flight turn but keeps the session alive and
idle — use this instead of agent_kill when you want to redirect the agent
rather than end it.
{ "tool": "agent_interrupt", "args": { "sessionId": "sess_abc123" } }
MCP: recovery
session_restart respawns an exited or killed session with conversation
continuity — it does not start fresh, it resumes.
{ "tool": "session_restart", "args": { "sessionId": "sess_abc123" } }
MCP: visibility and retention
{ "tool": "session_archive", "args": { "sessionId": "sess_abc123" } }
{ "tool": "session_unarchive", "args": { "sessionId": "sess_abc123" } }
Archiving hides a session from the default list; it's reversible via
session_unarchive. session_archive refuses to archive a still-live
session — kill or let it finish first.
{ "tool": "session_gc", "args": { "mode": "archive", "olderThanDays": 14 } }
Bulk archives (or bulk forgets, depending on mode) terminal sessions past a
retention window. Never touches sessions that are still live.
{ "tool": "session_set_keepalive", "args": { "sessionId": "sess_abc123", "keepalive": true } }
Exempts a session from the idle-reaper — use for a long-running background watcher you don't want auto-archived out from under you.
{ "tool": "session_set_pinned", "args": { "sessionId": "sess_abc123", "pinned": true } }
Pins a session so it stays at the top of listings and survives casual GC sweeps.
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.
- 1mo ago First seen · 109 lines · 77 tokens per session scan A 3495d60244ab
ap-lifecycle is a skill published in the GitHub repository agentproto/ts (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 1,039 once invoked, about $0.0003 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-04.
Other skills, from other repositories
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).
llm-wiki
Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) in plain markdown. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, critiquing a wiki source's reasoning, superseding stale knowledge, 'add to…
extract-wisdom
Extract wisdom, insights, and actionable takeaways from YouTube videos, blog posts, articles, or text files. Use when asked to extract wisdom or key insights from a given content source.
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.
home-assistant
This skill should be used when helping with Home Assistant setup, including creating automations, modifying dashboards, checking entity states, debugging automations, and managing the smart home configuration. Use this for queries about HA entities, YAML automation/dashboard generation, or troubleshooting HA issues.
deepeval
Use when discussing or working with DeepEval (the python AI evaluation framework).