Encrypted Multi-Provider Cloud Mirroring

    1

    Privacy-first apps let users keep their own storage instead of a backend that holds their data.

    $39

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Encrypted Multi-Provider Cloud Mirroring

    Example session with this skill installed

    I need to check the health of my encrypted backups across Google Drive and Dropbox and see if any files need repairing based on the manifest.

    • Read your context and instructions
    • Compiled the encrypted multi-provider cloud

    The system has completed a cross-provider audit against the encrypted manifest. One asset is currently at risk due to a hash mismatch on the primary provider.

    Replica Health Summary

    Object IDLevelHealthy ProvidersCorrupt/MissingNeeds RepairExplanation
    vault-001.encCRITICALdropboxgdrive (corrupt)YesSHA-256 mismatch on Google Drive.
    vault-002.encHEALTHYgdrive, dropboxNoneNoAll replicas match manifest hash.
    vault-manifest.encHEALTHYgdrive, dropboxNoneNoManifest integrity verified via AAD.

    Repair Plan

    • Task: repairReplica
    • Source: dropbox (Verified)
    • Target: gdrive
    • Action: Overwrite corrupt replica on gdrive with verified bytes from dropbox, then re-verify.

    Next steps

    1. Invoke createRepairPlan to generate the formal JSON plan for the CRITICAL asset.
    2. Call repairReplica using the dropbox connector as the source to restore gdrive.
    3. Re-run auditProvider for Google Drive to confirm the new SHA-256 matches the manifest.

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

    About this skill

    Privacy-first apps let users keep their own storage instead of a backend that holds their data. The hard parts are not the uploads: making sure the provider never learns names, hashes or keys; knowing when a replica is silently corrupt or missing; repairing it from another provider without ever decrypting; and storing the provider's refresh token safely on the device. This is that layer, independent of any one provider.

    Connector contract (connector.mjs): one interface for Google Drive, Dropbox, OneDrive, S3 or anything else; a shape check, a registry and an in-memory connector for tests and prototypes. Opaque-name enforcement (names.mjs) refuses any human-readable file name before upload.

    Mirroring and verification (mirror.mjs): upload the same bytes to several providers with per-provider failure isolation; verify a replica by downloading it and hashing (a provider's metadata hash is not proof), with constant-time comparison and verified/corrupt/missing/error outcomes; repair strictly from a replica that verified, never deleting the source; audit a provider listing against the manifest (present, missing, size mismatch, unexpected).

    Encrypted manifest (manifest.mjs): names, kinds, sizes and hashes encrypted with AES-256-GCM under the vault key with format-bound AAD, entries sorted, ciphertext hash-checked, tamper-evident.

    Token envelopes (token-envelope.mjs): refresh tokens wrapped under a separate key with the provider name in the AAD, so an envelope cannot be moved between providers.

    Health and policy (replica-health.mjs, sync-policy.mjs): per-object levels (healthy, degraded, critical, unknown) with a plain-language explanation, source selection by strategy (prefer-primary, first-verified, newest-verified), repair plans, an archive summary per provider, and a validated user policy (providers, minimum replicas, re-verification interval, metered and battery pauses).

    9 tests on the in-memory connector. reference/providers.md covers least-privilege scopes, PKCE, upload sessions, the five-step repair protocol and share semantics. Node 20+ WebCrypto, runs in browsers and workers too, no packages, no network in the package itself.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.

    Requires manual implementation of OAuth HTTP adapters. Does not perform content encryption. Does not support conflict-resolving sync for mutable files. Provider sees file sizes and timing.

    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 buying a skill.

    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 17 days ago

    Software
    Node.js 20+

    Permissions

    Terminal / Shell
    Listed17 days ago

    What's inside

    Frequently Asked Questions

    This skill provides a redundant storage layer that ensures your data is never locked into one provider. It protects against silent data corruption by using SHA-256 integrity checks and automatically repairs corrupted replicas on one cloud using verified data from another.

    The package includes the core mirroring logic, integrity verification protocols, encrypted manifest management, and a suite of functional tests. It also provides an in-memory connector and a template interface for building your own cloud API bridges.

    It is designed for Node.js 20+ environments and uses the WebCrypto API, making it compatible with modern backend services, edge workers, and browser-based AI agents. You will need to provide your own OAuth implementations for specific cloud providers like Google Drive or Dropbox.

    No, this skill operates on a zero-knowledge principle where data is encrypted client-side before being mirrored. The system manages the movement and repair of opaque ciphertext, meaning neither the transit layer nor the cloud providers can access the underlying content.

    Setup involves implementing the storage connector interface found in the provided scripts to link your specific cloud accounts. Once connected, you can immediately begin using the `mirrorCiphertext` and `createRepairPlan` functions to manage your multi-cloud replicas.

    New in APIs & Backend