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.
git clone --depth 1 https://github.com/oxygen-fragment/claude-modularWrote 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/commands/oxygen-fragment/claude-modular/rollback-procedure)<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>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.00000 | $0.00606 |
| Opus 5 | $0.00000 | $0.00303 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00061 |
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.
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
```
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.
- 7d ago First seen · 98 lines · 0 tokens per session scan A b73fb4cbc1ec
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.
Other commands, from other repositories
paul:help
Show available PAUL commands and usage guide.
paul:verify
Guide manual user acceptance testing of recently built features.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.
analizar-sesiones
Analizar sesiones de Claude en el equipo para extraer patrones de uso y generar recomendaciones de habilidades, plugins, agentes y reglas.
minar-referencias
Buscar repos open-source relevantes como referencia antes de implementar.