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 ash1794/vibe-engineering --skill vibe-rollback-plangit clone --depth 1 https://github.com/ash1794/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/ash1794/vibe-engineering/vibe-rollback-plan)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/vibe-rollback-plan"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/vibe-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/ash1794/vibe-engineering/vibe-rollback-plan"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/vibe-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.00056 | $0.00489 |
| Opus 5.5 | $0.00022 | $0.00196 |
| Sonnet 5.5 | $0.00011 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
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 17d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vibe-rollback-plan — 100% identical, 2 lines differ
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.
- 17d ago Changed · +27 tokens per session a784902b50e2
- 29d ago First seen · 79 lines · 29 tokens per session scan A 903efea01ec8
vibe-rollback-plan is a skill published in the GitHub repository ash1794/vibe-engineering (165 stars, last pushed 17d ago), licensed MIT. It adds 56 tokens to every session and 489 once invoked, about $0.0002 per session on Opus 5.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-09-26.
Other skills, from other repositories
cherry-regression-test
Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.
feature-verify
Feature verification (READ-ONLY, P0-P5). Use when: verifying feature behavior after deployment, validating API responses, diagnosing production issues, post-deploy smoke test. Not for: modifying data (use feature-dev), code review (use codex-review-fast), writing tests (use codex-test-gen), security audit (use…
test-health
Holistic test coverage measurement. Use when: assessing test health, measuring coverage trends, quantitative + qualitative test audit. Not for: running tests (use verify), reviewing test sufficiency only (use codex-test-review), generating tests (use codex-test-gen). Output: multi-dimensional dashboard with coverage…
test-review
Test coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
post-dev-test
Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.
pre-pr-audit
Pre-PR confidence audit with 5-dimension scoring. Use when: final check before commit/push/PR, evaluating PR readiness, assessing test quality + risk + coverage holistically. Triggers: pre-pr, readiness check, confidence audit, final verification, ready to PR, how confident. Not for: code review (use…