rollback-procedure

rollback-procedure is a command for Claude Code from oxygen-fragment/claude-modular. It costs 0 tokens per session (606 once invoked), scanned A, original, MIT.

An emergency workflow for returning a deployed application to an earlier version and checking that it works correctly afterward.

In plain words
What is it for?
Use it to select a previous version, restore services or data when needed, run smoke tests, verify data consistency, notify stakeholders, and document the incident.
Why use it?
It provides an organized response when a deployment causes failures, including service recovery, database checks, communication, and incident follow-up.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to select a previous version, restore services or data when needed, run smoke tests, verify data consistency, notify stakeholders, and document the incident.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/oxygen-fragment/claude-modular/rollback-procedure
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.

Clone the repo
git clone --depth 1 https://github.com/oxygen-fragment/claude-modular

Made for: Claude Code.

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-procedure

README.md
[![agentmods](https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/rollback-procedure.svg)](https://agentmods.dev/commands/oxygen-fragment/claude-modular/rollback-procedure)
Your own site
<a href="https://agentmods.dev/commands/oxygen-fragment/claude-modular/rollback-procedure"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/rollback-procedure.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 606 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.00000 $0.00606
Opus 5 $0.00000 $0.00303
Sonnet 5 $0.00000 $0.00121
Haiku 4.5 $0.00000 $0.00061

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

Security

Grade A, and why

rollback-procedure 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 7d 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.

.claude/commands/deployment/rollback-procedure.md · 98 lines

What it actually says

Rollback Procedure Command

2. **Rollback Planning**
   - Identify target rollback version
   - Assess data migration requirements
   - Plan service coordination and dependencies
   - Prepare rollback communication

3. **Service Rollback**
   - Stop affected services gracefully
   - Deploy previous version artifacts
   - Restart services in correct order
   - Verify service health and connectivity

4. **Database Rollback**
   - Assess database schema changes
   - Execute database rollback procedures
   - Restore data from backups if needed
   - Verify data consistency and integrity

5. **Validation and Testing**
   - Execute smoke tests on rolled-back system
   - Validate critical functionality
   - Test user authentication and core features
   - Verify external integrations

6. **Communication and Follow-up**
   - Notify stakeholders of rollback completion
   - Document lessons learned
   - Plan incident post-mortem
   - Update rollback procedures based on learnings
# Emergency rollback:
# - Immediate service rollback
# - Automated health checks
# - Stakeholder notification
# - Incident documentation
```

```bash
# Rollback to specific version
/deploy:rollback-procedure --version=1.2.2

# Targeted rollback:
# - Specific version restoration
# - Data migration assessment
# - Comprehensive validation
# - Controlled recovery
```

```bash
# Rollback with data preservation
/deploy:rollback-procedure --preserve-data

# Data-preserving rollback:
# - Service-only rollback
# - Database state maintained
# - Minimal user impact
# - Gradual recovery
```
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. 7d ago First seen · 98 lines · 0 tokens per session scan A b73fb4cbc1ec

Subscribe to this mod's changes

rollback-procedure is a command published in the GitHub repository oxygen-fragment/claude-modular (283 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 606 tokens. 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-30.