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 mracal/vibe-engineering --skill rollback-plangit clone --depth 1 https://github.com/mracal/vibe-engineeringWrote 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/mracal/vibe-engineering/rollback-plan)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/rollback-plan"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/rollback-plan/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/mracal/vibe-engineering/rollback-plan"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/rollback-plan.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.00462 |
| Opus 5.5 | $0.00012 | $0.00185 |
| Sonnet 5.5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
vibe-rollback-plan 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 1mo 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.
This is a copy
100% identical to vibe-rollback-plan — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
vibe-rollback-plan
The time to plan a rollback is BEFORE you need one.
When to Use This Skill
- Database migrations (especially destructive ones)
- API breaking changes
- Infrastructure changes (networking, permissions, DNS)
- Large dependency upgrades
- Any change where "undo" isn't obvious
When NOT to Use This Skill
- Safe, easily reversible changes (adding a new file, adding a feature flag)
- Changes with automated rollback (CI/CD with rollback built in)
- Local development changes
Steps
-
Document the change:
- What is being changed?
- Why is it being changed?
- What systems are affected?
-
Define success criteria:
- How do we know the change worked?
- What metrics to watch?
- How long to monitor before declaring success?
-
Assess blast radius:
- What breaks if this fails?
- Which users/services are affected?
- Is there data loss risk?
-
Write rollback procedure:
- Step-by-step commands to reverse the change
- Expected time to rollback
- Who needs to be notified?
-
Pre-change checklist:
- Rollback procedure documented
- Rollback tested (if possible)
- Monitoring in place
- Team notified
- Backup taken
Output Format
Rollback Plan: [Change Name]
Change: [Description] Risk Level: Low / Medium / High / Critical Blast Radius: [What's affected] Estimated Recovery Time: [Time to rollback]
Success Criteria
- [How to verify the change worked]
Rollback Procedure
# Step 1: [Description]
[command]
# Step 2: [Description]
[command]
Pre-Change Checklist
- Backup taken
- Rollback tested
- Monitoring active
- Team notified
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.
- 1mo ago First seen · 79 lines · 29 tokens per session scan A 903efea01ec8
vibe-rollback-plan is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed 13d ago), licensed MIT. It adds 29 tokens to every session and 462 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-rollback-plan, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
codexkit-repository-maintenance
Use when maintaining or improving the GameStudio-CodexKIT source repository, including CI, governance, catalog, generators, adapters, packaging, documentation, versioning, or release readiness.
release-candidate-preflight
Use when a release candidate or RC needs a go/no-go readiness decision across required artifacts, test summaries, known issues, approvals, compatibility, monitoring, and rollback.
studio-workspace-routing
Use when .agents/project-profile.yaml, nested Git roots, or cross-repository game work requires a profile-defined repository route, validation slice, or cross-project phase.
agent-sync-coordinator
Agent skill for sync-coordinator - invoke with $agent-sync-coordinator.
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.