Consented, Browser-Encrypted, Receiver-Owned Web Intake

    1

    Law firms, clinics, insurers and agencies need people to send them details and documents before anyone has met.

    $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

    Consented, Browser-Encrypted, Receiver-Owned Web Intake

    Example session with this skill installed

    Our law-firm clients want prospective clients to submit intake forms and photos online, but we must not be able to read them. Design the pipeline and tell me exactly what our server retains.

    • Read your context and instructions
    • Compiled the consented browser-encrypted receiver-owned

    Summary

    Pipeline wired with the reference implementation; the service holds hashes, counts and checksums only.

    What runs where

    Staff: confirm the mobile number and record consent for one transactional SMS; the invitation stores SHA-256(token), last four digits, language, practice area, expiry.

    Browser: exchanges the fragment token once for hashed session and CSRF cookies, encrypts each file and the answers with a fresh AES-256-GCM key wrapped to the firm's RSA-OAEP-256 public key, and PUTs ciphertext straight into the firm's bucket under quarantine/ with every signed header.

    Service: HEAD-verifies size, content type, checksum and metadata, writes one receipt (asset count, schema version, time), clears the session.

    Firm: lists receipts, fetches ciphertext with 60-second links, verifies SHA-256, decrypts with its private key in an isolated workspace, scans, then promotes.

    Retained by the service

    Token, session and CSRF hashes; phone last 4; organization, language, practice area, expiry, status; object ids, byte counts, SHA-256; receipts; audit events.

    Never retained

    Raw token, full phone number, any answer or name, attachment names or contents, browser drafts, the private key, plaintext copies. node --test scripts/intake.test.mjs proves it: 9 pass, including the test that dumps every table and finds none of those.

    Before go-live

    Firm key pair generated on their machine with two encrypted recovery copies; connector in testing until acceptance phases A, B and C pass.

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

    About this skill

    Law firms, clinics, insurers and agencies need people to send them details and documents before anyone has met. The usual intake form puts that content in the vendor's database. This pipeline keeps the vendor out, and its tests prove it by dumping every table after a submission and searching for the answers, the phone number, the filename and the token.

    The path: staff confirm the number and get separate consent for one transactional SMS; the link carries a 256-bit token in the URL fragment (never in access or referer logs); the page exchanges it once for hashed session and CSRF cookies and removes it from history; the browser encrypts each asset with a fresh AES-256-GCM key wrapped by the receiving organization's RSA-OAEP-256 public key, header bound as authenticated data, and PUTs the ciphertext straight into the organization's S3-compatible bucket under a quarantine prefix with every required header signed; the service verifies by HEAD (size, content type, checksum, metadata), writes one content-free receipt, and issues 60-second download links to the organization's credential.

    envelope.mjs (Node and browser): key pair generation, public-JWK validation that refuses any private field, encrypt, parse, decrypt (receiver side only). intake-service.mjs (node:sqlite): invitations with consent gates and last-four-digits retention, single-use exchange, rate limits, upload intents with limits and a unique payload index, completion with per-asset verification, receipts, downloads, connector lock after the first invitation, unimplemented connector kinds failing closed, an in-memory object store that behaves like a presigned bucket. sms.mjs: EN/ES invitation text with STOP wording and a body checker. templates/intake-form.html: the bilingual page.

    Reference: the retention boundary, S3 connector requirements with two production lessons (sign every header; compare sizes numerically), key custody and break-glass rotation, and the A1-A11 acceptance plan with receiver-side decrypt, scan and key drills. 9 tests. Node 22.5+, no packages, no network.

    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 Node 22.5+. Reference implementation uses SQLite; production requires S3-compatible storage. Service cannot scan for malware. No legal certification provided.

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

    Software
    node

    Permissions

    Read Files
    Terminal / Shell
    Write Files

    The reference code and tests run node against an in-memory SQLite database and an in-memory object store: no network, no environment variables, no writes outside the project. Your production deployment talks to your own SMS provider and the organization's bucket.

    Listed18 days ago

    What's inside

    Frequently Asked Questions

    This skill eliminates the risk of PII/PHI exposure by encrypting data directly in the user's browser using AES-256-GCM. Your backend never touches unencrypted files, reducing your compliance burden and ensuring you only store encrypted blobs and metadata.

    The package includes the core Node.js logic for session management, a secure HTML/JavaScript template for browser-side encryption, and a reference implementation for S3-compatible storage integration. You also receive a pre-configured verification suite to ensure zero-retention compliance.

    Yes, the skill is designed to work with any S3-compatible object store (such as AWS, Cloudflare R2, or DigitalOcean Spaces) that supports pre-signed URLs. You simply need to provide the public RSA key and bucket credentials during the initialization step.

    Because the data is encrypted before it leaves the client's browser, your server cannot scan files for viruses. The receiving organization must implement their own post-upload malware scanning and decryption workflows within their private infrastructure.

    The skill requires Node.js 22.5 or higher to leverage native Web Crypto and sqlite modules. It is designed to be agent-agnostic and can be integrated into any AI-driven workflow that supports standard REST APIs and SMS-based identity verification.

    New in APIs & Backend