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 sivang/sivan-claude-plugins --skill resurrectgit clone --depth 1 https://github.com/sivang/sivan-claude-pluginsWrote 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/sivang/sivan-claude-plugins/resurrect)<a href="https://agentmods.dev/skills/sivang/sivan-claude-plugins/resurrect"><img src="https://agentmods.dev/badge/skills/sivang/sivan-claude-plugins/resurrect/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/sivang/sivan-claude-plugins/resurrect"><img src="https://agentmods.dev/badge/skills/sivang/sivan-claude-plugins/resurrect.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.00065 | $0.00408 |
| Opus 5.5 | $0.00026 | $0.00163 |
| Sonnet 5.5 | $0.00013 | $0.00082 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade B, and why
resurrect scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Do not lecture. Read the files. What it actually says
Session Resurrection & Context Reload
Role: Lead Architect returning to a project with wiped memory. Reconstruct project state immediately from documentation.
Objective: Ingest project context, identify the critical path, and prepare for immediate coding.
Phase 1: Context Ingestion
Read and analyze the following files in order (if they exist):
README.md- High-level architectural understandingPROJECT_STATUS.md- What is finished and what is broken- Most recent
SESSION_HANDOFF_*.mdorCHANGELOG.md- Brain dump and reasoning from last session package.json/requirements.txt/Cargo.toml/pyproject.toml- Verify the stack
Phase 2: State Reconstruction
Based on the files above, answer immediately:
- Current Status: Dev, Debugging, or Refactoring mode?
- The "Active Wound": What exact problem or feature was being worked on when the session ended?
- The "Gotchas": Complex logic or bugs noted in the Handoff file to avoid breaking again.
Phase 3: Ready State
- Dependency Check: Based on config files, what install commands need to run? (
npm install,pip install, etc.) - Next Action: The single highest priority task from the Handoff file.
- Command Line: The exact command to start the dev server or run tests.
Execution Style
- Do not lecture. Read the files.
- Summarize the mission concisely.
- Provide the start command.
- Execute.
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 · 41 lines · 65 tokens per session scan B 5957e24ba97a
resurrect is a skill published in the GitHub repository sivang/sivan-claude-plugins (1 stars, last pushed 9mo ago), licensed MIT. It adds 65 tokens to every session and 408 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
session-handoff
Synthesizes the current session into a structured HANDOFF block for context transfer between sessions. Captures what was built, decisions made, and unresolved items.
autolearn
Use when a verified non-trivial fix lands or existing solution docs need refresh. Not for unverified fixes.
history-forget
Use when the user asks to remove a session or note from recall, or to unforget or list exclusions. Not for remote, credential, publish, deploy, or irreversible changes.
history-sync
Use when the user requests memory transfer to or from a named peer. Not for recalling a session: use history-recall. Not for store registration: use history-source-registry.
keep-why-continuous-capture
Use when a non-trivial change lands or is abandoned and its decision, rejected alternatives, and reason must be captured. Not for trivial or corrective changes: those belong in CHANGELOG.
history-source-registry
Use when a coding-agent session store is added or its format drifts, to document its layout, roles, quirks. Not for recalling a session: use history-recall. Not for peer transfer: use history-sync.