rollback-safety-planner

rollback-safety-planner is a skill for Codex from Eliyce/paqad-ai. It costs 29 tokens per session (836 once invoked), scanned A, original, MIT.

A planner that writes rollback procedures for high-risk changes. Rollback means returning a deployed system to an earlier working state when a change causes trouble.

In plain words
What is it for?
Use it on stories that are hard to reverse, affect a wide area, or involve migrations to define triggers, recovery steps, forward-only notes, and practice drills.
Why use it?
It makes the response to incidents less dependent on the person who implemented the change and exposes rollback difficulties before release.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it on stories that are hard to reverse, affect a wide area, or involve migrations to define triggers, recovery steps, forward-only notes, and practice drills.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/eliyce/paqad-ai/rollback-safety-planner
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 Eliyce/paqad-ai --skill rollback-safety-planner
Clone the repo
git clone --depth 1 https://github.com/Eliyce/paqad-ai

Made for: 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 rollback-safety-planner

README.md
[![agentmods](https://agentmods.dev/badge/skills/eliyce/paqad-ai/rollback-safety-planner/github.svg)](https://agentmods.dev/skills/eliyce/paqad-ai/rollback-safety-planner)
Your own site
<a href="https://agentmods.dev/skills/eliyce/paqad-ai/rollback-safety-planner"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/rollback-safety-planner/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 rollback-safety-planner

Your own site · 80×15
<a href="https://agentmods.dev/skills/eliyce/paqad-ai/rollback-safety-planner"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/rollback-safety-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 836 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.
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.00029 $0.00836
Opus 5 $0.00015 $0.00418
Sonnet 5 $0.00006 $0.00167
Haiku 4.5 $0.00003 $0.00084

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

Security

Grade A, and why

rollback-safety-planner 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 11d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/lint-output.sh, scripts/select-stories.sh), 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.

runtime/base/skills/rollback-safety-planner/SKILL.md · 78 lines

How it starts

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

What It Does

Reads the story plan and selects every story tagged reversibility: hard or blast-radius: wide. For each, drafts a concrete rollback procedure: trigger condition, time-to-rollback target, step list executable by the on-call without consulting the original implementer, forward-only recovery notes when applicable, and a drill plan.

The point is to prevent surprised rollback failures during incidents — an explicit procedure is required before any high-cost story can be marked ready.

Use This When

Use this immediately after the story-designer emits its plan in the graduated and full lanes. Skip stories where reversibility is easy and blast-radius is isolated. Always run for migration workflows.

Inputs

  • Read the story plan at story_plan_path first; identify each story's risk annotation.
  • Read the spec at spec_path when available so the rollback's scope can be validated against documented behavior.
  • Read canonical module docs in module_doc_paths for feature flag names, deployment conventions, and existing rollback patterns.
  • Read references/rollback-procedure-template.md before drafting any procedure so every required field is populated.

Procedure

  1. Run scripts/select-stories.sh <story_plan_path> [workflow] to get story ids needing a plan (filters on reversibility: hard, blast-radius: wide, or workflow=migration).
  2. For each selected story, draft a procedure with every field in assets/required-fields.txt (Trigger, Time-to-rollback, Steps, Verification, Forward-only, Drill).
  3. Feature-flag rollouts: list the flag name as step 1; confirm the flag exists in the project's flag registry, never invent one.
  4. Data migrations: describe forward-only recovery explicitly and call out permanently-lost data.
  5. Every step must be idempotent and verifiable — declare the post-step check inline.
  6. Format per assets/output.template.md; validate with scripts/lint-output.sh.

Output Contract

  • Match assets/output.template.md: ## Rollback Plans, per-story ### S-N — name with the 6 required fields, and a Coverage: footer.
  • When no stories require a rollback plan, output the literal Rollback Plans: none required (all stories have easy reversibility and isolated blast radius).
  • Output must pass scripts/lint-output.sh (exit 0).

Read the full file on GitHub · 78 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 78 lines · 29 tokens per session scan A ea094e5c118a

Subscribe to this mod's changes

rollback-safety-planner is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 836 once invoked, about $0.0001 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.