Cryptography Implementation Reviewer
$2.99OfficialReview cryptographic implementations: algorithm selection, key management, random number generation, and protocol-level flaws.
What you get
- ✓10-step procedure
- ✓6 pitfalls to avoid
- ✓Installs into 6 tools
- Version
- v1 →
- Last updated
- today
- Length
- 4 min read
- Requires
- Best with a strong model (Claude Sonnet 4)
Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes · Handles multi-file projects
Preview
When to use
Use this skill when reviewing code that uses cryptography: hashing, encryption, signing, key exchange, TLS configuration, JWT verification, password storage, or a custom protocol. It catches the implementation-level mistakes (wrong mode, bad IV, predictable randomness, key reuse) that a static "is AES secure?" check will miss. It is for review of existing code, not for designing new cryptographic primitives — never invent your own crypto.
Inputs to gather
- Source files under review: language(s), framework(s), and any crypto libraries in use (libsodium, OpenSSL/BoringSSL, Tink, java.security, PyCA cryptography).
- Threat model and security goal per operation: confidentia
…
🔒 Buy once ($2.99) to unlock the full playbook, download it, and install it in every tool you use.