More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Fallpath: Keep the app running when a vendor blocks you

    1

    Tells a paused database, spend cap or blocked deploy apart from a real bug, picks the cheapest fallback, backfills every table the app reads, verifies counts, then sets caps and a return date.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Fallpath: Keep the app running when a vendor blocks you

    Fallpath: Keep the app running when a vendor blocks you

    Example session with this skill installed

    Fallpath: our app shows Failed to fetch on every page since this morning and all screens are stuck on loading. Nothing was deployed.

    • Read your context and instructions
    • Compiled the fallpath

    Symptom: Failed to fetch, every page on its loading state, NXDOMAIN on the DB host. Matches the table: hosted DB project paused.

    Bills and caps: provider dashboard shows the project paused for an unpaid invoice (example). No code change made. Your call: pay, wait or fall back. You chose fall back.

    Fallback: local DB stack (supabase start on Docker, analytics off). Return to the original set for

    2026-11-02.

    Cutover notes

    • Target stood up by scripts/fallback-up.sh (in repo), 512MB
    • 23 migrations applied; 1 quirk fixed as a new migration (role grant for SET ROLE)
    • New DSN behind USE_FALLBACK_DB, default off, now on in .env.local
    • .env.local.* gitignored before creating; original env backed up outside the repo

    Backfill (4 tables, counts match)

    TableSourceFallback
    orders48,21048,210
    users3,9043,904
    sessions12,77512,775
    report_cache (runtime-created)610610, unique index recreated

    Verify: health endpoint DB ok · protected routes 401 · UI shows real orders.

    Cost guards: budget alerts at 80% and 95% added.

    Next steps

    1. Settle the invoice, then repoint the DSN and backfill the delta.
    2. Run supabase stop once the original is back.
    3. If you keep the fallback, document it before 2026-11-02.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    When every page hangs on loading or the console says "Failed to fetch", the natural move is to debug the code. Often the real cause is a vendor: a paused database, a spend cap, a host refusing deploys or CI minutes used up, and hours go into a fix that was never in the code. Fallpath is a playbook for telling a vendor block apart from a bug and keeping the app running without losing data.

    What it does

    • Symptom table maps errors to likely vendor causes, such as NXDOMAIN on the DB host, a scrape returning 0 items, a deploy 403 or a CI job failing in about 2 seconds.
    • Bills first checks dashboards, balances and caps before any code change; pay, wait or fall back stays your call.
    • Cheapest fallback such as a local DB stack, free-tier serverless Postgres, a small temporary Postgres or a self-hosted tool, with a return date set at the start.
    • Scripted target with every migration applied and provider quirks fixed as new migrations.
    • Full backfill of every table the app and downstream consumers read, with unique indexes recreated.
    • Cost guards: rolling caps, kill switches, cadence and 80% and 95% alerts.

    How it works

    1. Name the symptom and confirm the vendor cause with evidence.
    2. Pick the fallback and wire it behind env flags that default off.
    3. Backfill and verify: row counts match, protected endpoints return 401 not 500, the UI shows real data.
    4. Guard the env swap, then stop old compute and resize or delete disks.
    5. Restore or adopt by the return date.

    Frameworks & tools

    Examples named in the skill: Supabase local stack on Docker, OrbStack or colima, Neon, Fly Postgres, psql, yt-dlp and Playwright scrapers.

    Why this beats prompting it yourself

    A generic prompt goes straight to the code. This skill checks billing first, sizes the fallback for the backfill (a 256MB Postgres crash-looped on about 260k rows), and inventories every table so other screens do not end up empty.

    Use cases

    • Paused database in the middle of a demo or launch.
    • Scraper returning 0 because of a cap or a link shape.
    • Host blocked or CI minutes exhausted.
    • Cost trim without an outage.

    Known limitations

    Not for errors that reproduce against a healthy service or for normal releases. Billing decisions stay with you, and stopping old compute or deleting data needs your go-ahead.

    Not for errors that reproduce against a healthy service or for normal releases. Billing decisions stay with you, and stopping old compute or deleting data needs your go-ahead.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    Requires

    Supabase CLI
    Docker
    psql
    Neon
    Fly Postgres

    Permissions

    Browser
    Read Files
    Listed29 days ago

    What's inside

    Frequently Asked Questions

    Access to the provider dashboard or billing pages, the repo, and the database migrations. The fallback options it uses as examples include a local Supabase stack, Neon and Fly Postgres.

    No. Billing is your call (pay, wait or fall back), and stopping old compute or deleting data needs your go-ahead.

    It checks bills and caps before touching code, then backfills and verifies every table the app reads, and sets a return date so the fallback does not become permanent by accident.

    SKILL.md, the instructions your agent follows, and LICENSE.md.

    New in DevOps & Cloud