vnsh

Encrypt files and publish temporary URL-fragment protected blobs for client-side decryption.

155|23|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/raullenchai/vnsh --skill vnsh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vnsh
Source: https://github.com/raullenchai/vnsh/tree/main
Command: npx skills add https://github.com/raullenchai/vnsh --skill vnsh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, openssl, and includes scripts (resource) components.

What problem does it solve?

vnsh provides ephemeral, host-blind encrypted sharing to securely transfer data to AI agents or collaborators without exposing plaintext on servers.

Core Features & Use Cases

  • Secure CLI uploads: generate a short-lived vnsh.dev URL that decrypts client-side.
  • Read decrypted content from vnsh URLs via web viewer or MCP, enabling seamless AI workflows.
  • Ephemeral TTL: automatic expiration and data vaporization after TTL.

Quick Start

Upload a file with vnsh to obtain a secure, expiring link that you can share with teammates.

Frequently Asked Questions about vnsh

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I securely share encrypted files with an AI agent using a CLI?

Ephemeral encrypted file sharing uses a host-blind storage model where ciphertext is uploaded to a dumb storage layer and 32-byte keys with 16-byte IVs are encoded in URL fragments for client-side decryption.

Can I read and decrypt vnsh URLs directly within an MCP workflow?

Yes, MCP workflows support reading vnsh URLs to decrypt content seamlessly within AI contexts, allowing agents to retrieve and decode ciphertext directly without exposing plaintext on servers.

Does secure ephemeral file sharing require any specific dependencies to encrypt and publish data?

Secure ephemeral file sharing requires curl and openssl dependencies to encrypt local files and publish the ciphertext blob to the dumb storage layer before generating the URL fragment protected link.

What is the best way to automatically expire sensitive data shared with collaborators?

The best way to automatically expire sensitive data is using an ephemeral TTL window that ensures automatic expiration and data vaporization after 24 hours, keeping plaintext off servers entirely.

What are the limitations of using URL fragment protected blobs for secure sharing?

Limitations of URL fragment protected blobs include a strict 24-hour ephemeral TTL window before data vaporization occurs and the requirement of client-side decryption, meaning recipients must have proper tools to decode the ciphertext.