verify-bundle
Checks file integrity against manifest hashes and validates OpenTimestamps proofs.
Install
mkdir -p .claude/skills/verify-bundle && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11797" && unzip -o skill.zip -d .claude/skills/verify-bundle && rm skill.zipInstalls to .claude/skills/verify-bundle
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when re-hashing evidence and verifying against recorded hashes and OpenTimestamps proofs.Key capabilities
- →Re-hash files to confirm evidence integrity
- →Compare re-hashed files against recorded manifests
- →Validate BagIt manifests
- →Verify OpenTimestamps proofs for immutability
- →Detect accidental or malicious file modifications
- →Aggregate verification results into a PASS/FAIL report
How it works
The skill re-hashes files and compares them against recorded manifests, validates BagIt manifests, and verifies OpenTimestamps proofs. It aggregates these results into a single PASS/FAIL report.
Inputs & outputs
When to use verify-bundle
- →Validate BagIt evidence integrity
- →Audit chain-of-custody milestones
- →Verify OpenTimestamps anchors
- →Detect accidental file modifications
About this skill
Verify Bundle
Re-hash files and compare against recorded hashes, validate BagIt manifests, and verify OpenTimestamps proofs.
When to use
- Confirming evidence integrity after transfer or archival
- Detecting accidental or malicious file modifications
- Auditing chain-of-custody milestones before handoff
- Validating OpenTimestamps anchors for immutability proof
Inputs to gather
- Path to evidence directory, BagIt bag, or individual file (required)
Procedure
- If input is a BagIt bag (contains
bagit.txt): runbagit.py --validate <dir>. - If input is a directory with a
.sha256manifest: re-runfind <dir> -type f -exec sha256sum {} \;, compare output against manifest entries usingdiff. - For any
.otsfiles found in or near the evidence: runots verify <file>on each. - Aggregate results into a single PASS/FAIL report:
- All files match recorded hashes: PASS
- Any divergence: FAIL with per-file diff detail
- All OpenTimestamps proofs valid: noted
- Any OTS verify failure: FAIL with reason
- Report to user: overall status, per-file divergence (if any), OTS proof validity, and recommendation (re-bag if needed, or escalate if tampering suspected).
Output / side effects
- Verification results printed to stdout (no files modified).
- User sees: PASS/FAIL status, detailed divergence if any, OTS validity.
- Read-only on all input files.
Safety / constraints
- This is a forensic read-only operation; it does not modify evidence.
- Verification failure does not imply intentional tampering; check for accidental overwrites, encoding changes (e.g., video transcoding), or filesystem timestamp updates.
- For large evidence sets, verification may take several minutes; inform user.
- OpenTimestamps verification requires the
.otsfiles to be present alongside originals.
When not to use it
- →When the task is not about verifying evidence integrity
- →When the task involves modifying evidence
- →When OpenTimestamps verification is not required
Limitations
- →This is a forensic read-only operation; it does not modify evidence
- →Verification failure does not imply intentional tampering
- →OpenTimestamps verification requires the .ots files to be present alongside originals
How it compares
This skill automates the forensic verification of digital evidence using hashing and OpenTimestamps, providing a structured integrity check beyond simple file comparisons.
Compared to similar skills
verify-bundle side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| verify-bundle (this skill) | 0 | 3mo | No flags | Intermediate |
| reverse-engineering-tools | 73 | 4mo | No flags | Advanced |
| game-hacking-techniques | 42 | 2mo | No flags | Advanced |
| solidity-security | 15 | 2mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
reverse-engineering-tools
gmh5225
Guide for reverse engineering tools and techniques used in game security research. Use this skill when working with debuggers, disassemblers, memory analysis tools, binary analysis, or decompilers for game security research.
game-hacking-techniques
gmh5225
Guide for game hacking techniques and cheat development. Use this skill when researching memory manipulation, code injection, ESP/aimbot development, overlay rendering, or game exploitation methodologies.
solidity-security
wshobson
Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.
1password
openclaw
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
senior-security
davila7
Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.
ghidra
mitsuhiko
Reverse engineer binaries using Ghidra's headless analyzer. Decompile executables, extract functions, strings, symbols, and analyze call graphs without GUI.