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 agentmods add commands/iampawan/manifest/rollback-checkgit 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/commands/iampawan/manifest/rollback-check)<a href="https://agentmods.dev/commands/iampawan/manifest/rollback-check"><img src="https://agentmods.dev/badge/commands/iampawan/manifest/rollback-check.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 | $0.00040 | $0.00438 |
| Opus 5 | $0.00020 | $0.00219 |
| Sonnet 5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
rollback-check 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 4d 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-check
Runs the rollback-guard skill for a contract that is currently rolling out. Samples Sentry errors, crash-free rate, release adoption, and perf against the contract's budgets, and returns a recommendation.
Usage
/rollback-check SC-005
What it does
- Reads the contract's budgets (
perfBudget, crash-free / error budgets, optionalrollbackTriggers). - Samples live signals via Sentry / Crashlytics / APM for the rollout window.
- Emits a schema-checked verdict (
scripts/validate.mjs --check-guard):- proceed — healthy, keep ramping.
- hold — a warning or low confidence; pause the ramp, investigate.
- recommend-rollback — a clear breach; recommends reverting and posts a top-level Slack alert to the owner.
- Writes a guard report and stamps
guardVerdicton the contract.
Important
This command recommends; it never acts. Pausing a canary, flipping a flag, or rolling back is a production change a human approves and performs. The guard gives you the defensible call and the exact action to take — you pull the trigger.
When to use
- Manually, any time during a rollout you want a health read.
- Automatically on a tight cadence via
rollback-guard.ymlwhile a canary is live (canaryStartedAtset,prodRollout100Atnot yet).
See also
/verify-deploy— pre-rollout readiness verdict/launch— the slower day 1/7/14/28 "did it land" reportsreference/CONTRACT-FORMAT.md—rollbackTriggers+ guard fields
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.
- 4d ago First seen · 49 lines · 40 tokens per session scan A 04dc5288590c
rollback-check is a command published in the GitHub repository iampawan/Manifest (5 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 438 once invoked, about $0.0002 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.