- Home
- Skills
- APIs & Backend
- Portable Evidence Packet with SHA-256 Manifest
Portable Evidence Packet with SHA-256 Manifest
This kit is the packet format, the tool that writes it, the tool that checks it, and the words that keep its claims honest.
$29
Works with the AI Agents you already use
Portable Evidence Packet with SHA-256 Manifest
Example session with this skill installed
Our tenants' app lets people collect photos and PDFs for a deposit dispute. Give them an export their lawyer can verify wasn't altered, without us claiming anything we can't back up.
- Read your context and instructions
- Compiled the portable evidence packet
Summary
Added a verifiable packet export: an ordinary ZIP with a manifest that names every original by SHA-256 and byte count, keeps originals byte-exact, keeps the tenant's notes separate, and carries a disclosure saying exactly what the packet does and does not prove.
Create
node scripts/packet.mjs create --title "Deposit dispute, 14 Oak St" --context "Move-out photos and the deposit statement" --out packet.zip --original IMG_0012.JPG --original IMG_0013.JPG --mime image/jpeg --original statement.pdf --note "Photos taken 1 Oct at move-out; statement arrived 9 Oct by email"
wrote packet.zip: 3 original(s), 1 note(s), manifest sha256 7c1e4f...a2d9
The manifest hash was recorded separately and timestamped with an RFC 3161 authority, so "existed by 29 Oct" can be shown later.
What the lawyer does
node scripts/packet.mjs verify packet.zip -> ok: packet.zip is consistent with its manifest (6 files), or without the tool: unzip, sha256sum originals/*.bin, compare with manifest.json.
What a tampered copy looks like
One byte changed in a photo: FAIL: packet.zip / original 2b7f...: SHA-256 does not match the manifest, exit 1. A file added to the archive: originals/extra.bin is in the archive but not in the manifest.
What the packet says about itself
README.txt and the manifest carry the disclosure: unsigned, unencrypted, not an authentication, not a timestamp, not a claim of admissibility; filenames and notes are untrusted content. The provider-reported filename (IMG_0012.JPG) is stored as data; the archive path is an id, so a hostile filename can never become a path on the recipient's machine.
Tests
node --test scripts/packet.test.mjs: 5 passed, including the ZIP reader's refusals and a tampered-packet CLI run.
Connects securely to your tools. The creator never sees your data.
About this skill
People need to hand a bundle of files to a lawyer, an insurer, a landlord or a court with a way to check that nothing was altered after export, without pretending the bundle is more than it is. This kit is the packet format, the tool that writes it, the tool that checks it, and the words that keep its claims honest.
Format (reference/format.md, evidence-packet/1): manifest.json, README.txt, originals/<uuid>.bin stored byte for byte without recompression, notes/<uuid>.txt kept apart from source material. The manifest records provider name and media type as data, exact bytes, SHA-256, device-clock import and export times as observations, the nullable provider-modified time, a safe archive path per file, and the disclosure verbatim: unsigned, unencrypted, not an authentication, not a timestamp, not a claim of admissibility.
zip-lite.mjs: a ZIP writer and reader on node:zlib alone (stored and deflated, CRC-32) whose reader refuses absolute and traversal names, backslashes, NUL, case-insensitive duplicates, encrypted entries, unsupported methods, a central directory that does not account for every byte, and size or CRC mismatches.
packet.mjs: create (title, context, originals with provider names, notes; prints the manifest's SHA-256 for a separate record or an RFC 3161 timestamp; never overwrites), verify (every referenced file present under the right folder with matching bytes and hash, nothing unreferenced, right schema, disclosure present; exit 0 or 1, problems named, --json), show. Library exports for your own app.
5 offline tests including the ZIP layer's refusals and a tampered-packet CLI run. Node 20+, 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.
No ZIP64 support (4GB/65k file limit). No built-in encryption or digital signatures. Requires Node 20+.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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 19 days ago
- Software
Node.js 20+
- Optional
- SHA-256 utility
A SHA-256 utility is only needed to verify outside the tool.
Permissions
Shell to run the node script and tests; read files for the originals; write files for the packet ZIP (never overwriting an existing one). No network access, no environment variables.