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 agentmods add skills/sivang/sivan-claude-plugins/doomsdaynpx skills add sivang/sivan-claude-plugins --skill doomsdaygit 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/doomsday)<a href="https://agentmods.dev/skills/sivang/sivan-claude-plugins/doomsday"><img src="https://agentmods.dev/badge/skills/sivang/sivan-claude-plugins/doomsday.svg" alt="Measured on agentmods" 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.00055 | $0.00579 |
| Opus 5 | $0.00028 | $0.00290 |
| Sonnet 5 | $0.00011 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
doomsday 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 5d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
End of Session Shutdown Protocol (Doomsday Prep)
Role: Paranoid Lead Architect and Project Manager.
Objective: Secure project state, update all documentation, and prepare a comprehensive handoff. Treat this as if the server is about to be wiped and rebuild must happen from these files alone.
Phase 1: Execution & File Integrity
- Force Save: Ensure every code block, text buffer, or conceptual change discussed is written to its respective file. Leave nothing in "memory" only.
- File Creation: If new files were discussed but not generated, generate them now.
Phase 2: Documentation Synchronization
Update the following .md files immediately. Create them if they do not exist:
A. Update README.md
- Reflect the current state of the application
- Update installation or usage instructions if dependencies changed
- Add a "Recent Changes" section summarizing this session's work
B. Update/Create PROJECT_STATUS.md
- Current Phase: Where exactly are we? (Dev, Testing, Refactoring)
- Completed: Bullet points of everything achieved this session
- In Progress: What is half-baked? (Mark clearly to avoid deploying broken code)
- Blockers: Any bugs or issues that couldn't be solved today
C. Update User/Dev Docs
- If API endpoints changed, update API documentation
- If UI logic changed, update user guides
Phase 3: The Brain Dump (Context Preservation)
Create SESSION_HANDOFF_[DATE].md (or append to CHANGELOG.md). Include:
- The "Why": Briefly explain why specific architectural decisions were made today
- The "Gotchas": Note weird bugs or workarounds that might be forgotten
- Next Actions: Strictly prioritized list of exactly what to do first next session
Phase 4: Version Control Prep
- Generate a comprehensive Git Commit Message formatted as:
feat/fix/chore: [Summary][Bulleted list of detailed changes]
- Do NOT run the commit command unless instructed, but provide exact commands to stage and commit safely.
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.
- 5d ago First seen · 60 lines · 55 tokens per session scan A 770dfc827760
doomsday is a skill published in the GitHub repository sivang/sivan-claude-plugins (1 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 579 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
fleet
Parallel campaign orchestrator. Runs multiple campaigns in coordinated waves within a single session. Spawns 2-3 agents per wave in isolated worktrees, collects discoveries, shares context between waves. Use when work decomposes into 3+ independent streams that can run simultaneously.
daemon
Continuous autonomous operation mode. Keeps campaigns running 24/7 by chaining Claude Code sessions via RemoteTrigger. Each session picks up from the campaign's continuation state, works until context runs low or the phase completes, then schedules the next session. Auto-stops on campaign completion or budget…
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
setup
First-run experience for the harness. Three modes: Recommended (guided, 3 min), Full Tour (guided + skill walkthrough, 8 min), and Express (zero questions, 30 sec). Installs hooks first, detects stack, configures harness.json, runs a live demo on real code, and prints a reference card.
evolve
Research-driven multi-cycle improvement director. Forms causal hypotheses about why scores are low, validates them with scout agents before attacking, dispatches axis-parallel fleet attacks, extracts transferable patterns, and runs indefinitely within a budget envelope. Accumulates a persistent belief model and…
research
Focused research investigations. Converts questions into structured findings with confidence levels and source citations. Single agent by default; with --parallel (or when the question decomposes into 3+ independent angles) it spawns scout agents whose findings are compressed into a unified brief. Does not make…