Customer-Owned Data Export with Sealed Copies

    1

    Give customers their data in forms they can trust without you: a ZIP of formula-safe CSVs with a hashed manifest, a passphrase-sealed copy (scrypt + AES-256-GCM) whose authenticated recipe header opens with OpenSSL, and a public-key-sealed copy for backups the server can never open; CLI

    $35

    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 CLIMuseMuseDotsDots+21 more

    Customer-Owned Data Export with Sealed Copies

    Example session with this skill installed

    I need to export two tables, 'users' and 'billing', for a customer named 'Acme Corp'. The customer provided a public key for a scheduled backup. Generate the command to seal this to their key.

    • Read your context and instructions
    • Compiled the customer-owned data export
    • Generated the data export

    The export process will first generate a sanitized ZIP containing your tables, then seal it using the customer's RSA public key. This ensures only the holder of the private key can access the data.

    Sealed Export Configuration

    StepActionCommand / Method
    1Generate Keysnode scripts/export-cli.mjs keygen --out-dir ./customer_keys
    2Export Datanode scripts/export-cli.mjs export --tables data.json --out acme_raw.zip
    3Seal to Keynode scripts/export-cli.mjs seal-to-key --in acme_raw.zip --out acme_backup.sealed --key ./customer_keys/public.pem
    4Verifynode scripts/export-cli.mjs inspect --in acme_backup.sealed

    Inspection Metadata Output

    {
      "format": "sealed-copy/public-key",
      "header": {
        "version": 1,
        "product": "Acme Corp Data Export",
        "created": "2023-10-27T10:00:00Z",
        "algorithm": "AES-256-GCM",
        "key_wrap": "RSA-OAEP-SHA256",
        "plaintext_hash": "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
      },
      "ciphertext_size": 4096128
    }
    

    Next steps

    • Provide the acme_backup.sealed file and the HOW-TO-OPEN.txt guide to the customer.
    • Ensure the customer has safely stored their private.pem file off-site.
    • Run the internal test suite node --test scripts/export.test.mjs to confirm environment compatibility.

    acme_raw.zip

    CSV · data export

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    A customer who keeps their records in your system has three different fears: "take a copy now before I do something risky", "give me my data in a form I can read if you disappear", and "give me a sealed copy to keep off your servers that you cannot open". One backup button answers none of them.

    Export (export.mjs, zip.mjs): one CSV per table, formula injection neutralized (values starting with =, +, -, @, tab or CR are prefixed and quoted), a README that says nothing from your software is needed, and MANIFEST.json with row counts, columns and SHA-256 per file, in a correct minimal ZIP (CRC-32, UTF-8 names, deflate only when it helps, unsafe names refused); a reader verifies CRCs and verify re-hashes against the manifest.

    Passphrase-sealed copy (sealed.mjs): scrypt (N=2^15) of the NFKC-normalized passphrase, AES-256-GCM, a plain JSON header holding the full recipe (KDF parameters, salt, IV, plaintext hash and size, label, date) so a clerk can rebuild the key years later with OpenSSL or Python. The header bytes are the GCM additional authenticated data and the tag has its own field, so altering one byte of the recipe or the recorded hash makes the file refuse to open instead of opening to the wrong answer. A how-to-open note is generated from the header.

    Public-key-sealed copy: for schedules when the passphrase is not available; the owner keeps an RSA private key (3072 generated, 2048 minimum, optional passphrase) and gives you the public half; each archive gets a fresh AES-256 key wrapped with RSA-OAEP(SHA-256). The system that wrote it cannot open it.

    CLI (export-cli.mjs): export, verify, seal, open, keygen, seal-to-key, open-with-key, inspect; passphrases from files, never argv. 6 tests: formula-safe CSV, ZIP round trip with corruption and unsafe-name refusals, manifest hashes, passphrase sealing with NFKC, wrong passphrase, header tampering, bit flip and the note, public-key sealing with the wrong key, a protected private key and a too-small key, and the CLI end to end. reference/three-fears.md explains the design and the wording for the UI.

    Node 18+, no packages, no network.

    Does not support ZIP64 or internal ZIP encryption. Large files may exceed memory limits as sealing currently processes data in memory. Node 18+ required.

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

    Requires

    Node.js 18+

    Permissions

    Read Files
    Write Files
    Listed17 days ago

    What's inside

    Frequently Asked Questions

    This skill provides a secure way to offer data portability by generating formula-safe CSVs and cryptographically sealed backups that even the service provider cannot decrypt, preventing vendor lock-in.

    The skill is designed for Node.js 18+ environments and works seamlessly with any AI agent or backend framework capable of executing standard Node.js scripts without external npm dependencies.

    You receive the full source code for the dependency-free Node.js implementation, including functions for CSV sanitization, SHA-256 integrity manifesting, and both symmetric and asymmetric encryption wrappers.

    No, the implementation relies strictly on built-in modules like `node:crypto`, meaning you can drop the code into your project and run it immediately without running `npm install`.

    The current version is optimized for standard business data exports; however, because it processes files in memory, it is not currently recommended for multi-gigabyte ZIP64 archives.

    It utilizes AES-256-GCM for authenticated encryption and scrypt for key derivation, ensuring that backups remain secure and accessible to the customer long-term without requiring your specific software.

    New in APIs & Backend