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 elevanaltd/HestAI-MCP --skill rollback-orchestrationgit clone --depth 1 https://github.com/elevanaltd/HestAI-MCPWrote 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/elevanaltd/hestai-mcp/rollback-orchestration)<a href="https://agentmods.dev/skills/elevanaltd/hestai-mcp/rollback-orchestration"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/rollback-orchestration/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/elevanaltd/hestai-mcp/rollback-orchestration"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/rollback-orchestration.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.00000 | $0.00630 |
| Opus 5 | $0.00000 | $0.00315 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
rollback-orchestration 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_ORCHESTRATION=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Deployment rollback planning, testing procedures, and data migration rollback strategies"
§1::CORE AUTHORITY::ADVISORY[rollback_plan_completeness⊕rollback_test_coverage] SCOPE::rollback_planning⊕rollback_testing⊕data_migration_reversal⊕deployment_strategy MISSION::"Ensure every deployment has a tested rollback plan before proceeding"
§2::PROTOCOL
ROLLBACK_PLAN_REQUIREMENTS::[ TRIGGER_CRITERIA::define_conditions_that_initiate_rollback<error_rate⊕latency_spike⊕data_corruption>, DECISION_AUTHORITY::who_approves_rollback<on_call⊕team_lead⊕automated>, SEQUENCE::ordered_steps_to_reverse_deployment, VERIFICATION::how_to_confirm_rollback_succeeded, COMMUNICATION::notification_plan<stakeholders⊕consumers⊕status_page>, TIME_BOUND::maximum_acceptable_rollback_duration ]
ROLLBACK_TESTING::[ PRE_DEPLOY::execute_rollback_in_staging<verify_procedure_works>, SIMULATE::inject_failure_condition→trigger_rollback→verify_recovery, VALIDATE::data_integrity_post_rollback<no_orphaned_records⊕no_corruption>, MEASURE::rollback_duration<must_be_within_time_bound> ]
DATA_MIGRATION_ROLLBACK::[ REVERSIBLE::design_migrations_with_down_path<additive_preferred>, IRREVERSIBLE::flag_destructive_migrations<column_drops⊕data_transforms>, STRATEGY::backup_before_migrate→verify_backup_restorability, DUAL_WRITE::consider_dual_write_period_for_critical_tables ]
DEPLOYMENT_STRATEGIES::[ SERVICE_BY_SERVICE::independent_rollback_per_service, ATOMIC::all_or_nothing_rollback<monolith⊕tightly_coupled>, CANARY::rollback_canary_only<progressive_deployment>, BLUE_GREEN::switch_back_to_previous_environment, SELECTION::match_strategy_to_architecture⊕risk_level ]
§3::GOVERNANCE
NEVER::[ deploy_without_rollback_plan, skip_rollback_testing_in_staging, assume_migration_is_reversible_without_verification, rollback_without_data_integrity_check ]
ESCALATION::irreversible_migration_detected→technical-architect
§5::ANCHOR_KERNEL TARGET::tested_rollback_plan_for_every_deployment NEVER::[deploy_without_rollback_plan,skip_rollback_testing,assume_reversibility,rollback_without_data_check] MUST::[define_rollback_triggers_and_authority,test_rollback_in_staging,verify_data_integrity_post_rollback,match_strategy_to_architecture] GATE::"Has the rollback plan been tested in staging and verified for data integrity?"
===END===
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 · 64 lines · 0 tokens per session scan A 6548e824d8b6
rollback-orchestration is a skill published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 630 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-09-03.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…