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 iampawan/Manifest --skill rollback-guardgit clone --depth 1 https://github.com/iampawan/ManifestWrote 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/iampawan/manifest/rollback-guard)<a href="https://agentmods.dev/skills/iampawan/manifest/rollback-guard"><img src="https://agentmods.dev/badge/skills/iampawan/manifest/rollback-guard.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.00088 | $0.02019 |
| Opus 5 | $0.00044 | $0.01009 |
| Sonnet 5 | $0.00018 | $0.00404 |
| Haiku 4.5 | $0.00009 | $0.00202 |
Grade A, and why
rollback-guard 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 8d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rollback guard
verify-deployment decides whether a build is ready to start rolling
out. You are the watcher for the period after that — while the
feature ramps from canary to 100%, you keep asking "is this still
healthy, or is it quietly on fire?" and surface a clear recommendation
the moment it stops being healthy.
You recommend; you do not act. Pausing a canary or rolling back is a
production change with blast radius — a human approves and performs it
(or flips the flag). Auto-executing a rollback is out of scope by
design, and matches verify-deployment's "don't auto-rollback" stance.
Inputs
- Contract ID (+ revision)
- Optional: explicit time window (default: since
canaryStartedAt, or the last 30 min if a tighter sample is requested)
When you should run
While a contract is in its rollout window: canaryStartedAt is set
and prodRollout100At is not — or it just reached 100% and you're in
the first 24h of full traffic. Outside that window, the slower
launch-report cadence (day 1/7/14/28) takes over. The
rollback-guard.yml workflow runs you on a tight cadence during that
window; /rollback-check <ID> triggers you manually.
Process
1. Read the contract's budgets
From .manifest/contracts/<ID>.r<N>.md, pull the thresholds you'll
judge against. These come from existing fields plus an optional
rollbackTriggers block:
- Per-behavior
perfBudget(latency / render / cold-start numbers). - The crash-free / error-rate budget if declared.
- Optional
rollbackTriggersfrontmatter (explicit guardrails):
rollbackTriggers:
errorRateMultiplier: 3 # error rate > 3× pre-launch baseline → breach
crashFreeFloor: 99.0 # crash-free users % must stay ≥ this
newIssueSeverity: blocker # any new Sentry issue at/above this → breach
minAdoptionForSignal: 0.05 # ignore noise until ≥5% of users are on the release
If rollbackTriggers is absent, fall back to sensible defaults
(error rate > 3× baseline, crash-free < 99%, any new high-volume
unhandled-exception issue), and say in the report that defaults were
used.
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.
- 8d ago First seen · 185 lines · 88 tokens per session scan A 19ae3ab45d55
rollback-guard is a skill published in the GitHub repository iampawan/Manifest (5 stars, last pushed 6d ago), licensed MIT. It adds 88 tokens to every session and 2,019 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…