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 Eliyce/paqad-ai --skill rollback-safety-plannergit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/rollback-safety-planner)<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.
<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>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.00029 | $0.00836 |
| Opus 5 | $0.00015 | $0.00418 |
| Sonnet 5 | $0.00006 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00084 |
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.
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 — 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_pathfirst; identify each story's risk annotation. - Read the spec at
spec_pathwhen available so the rollback's scope can be validated against documented behavior. - Read canonical module docs in
module_doc_pathsfor feature flag names, deployment conventions, and existing rollback patterns. - Read
references/rollback-procedure-template.mdbefore drafting any procedure so every required field is populated.
Procedure
- Run
scripts/select-stories.sh <story_plan_path> [workflow]to get story ids needing a plan (filters onreversibility: hard,blast-radius: wide, or workflow=migration). - For each selected story, draft a procedure with every field in
assets/required-fields.txt(Trigger, Time-to-rollback, Steps, Verification, Forward-only, Drill). - Feature-flag rollouts: list the flag name as step 1; confirm the flag exists in the project's flag registry, never invent one.
- Data migrations: describe forward-only recovery explicitly and call out permanently-lost data.
- Every step must be idempotent and verifiable — declare the post-step check inline.
- Format per
assets/output.template.md; validate withscripts/lint-output.sh.
Output Contract
- Match
assets/output.template.md:## Rollback Plans, per-story### S-N — namewith the 6 required fields, and aCoverage: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).
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.
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.
- 11d ago First seen · 78 lines · 29 tokens per session scan A ea094e5c118a
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.
Other skills, from other repositories
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-go
A command that implements code from a SPEC, a document describing the required behavior and work.
auto-plan
A code-planning skill that examines a codebase and creates a detailed specification, implementation plan, and acceptance criteria. It can organize requirements using EARS, a structured way to describe how software should behave in different situations.
agent-pipeline
Multi-agent pipeline orchestration skill.
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.