crypto

Detect cryptography anti-patterns in application security code during pull request reviews.

Updated May 15, 2026
One-click install
npx skills add https://github.com/mattnowdev/super-review --skill crypto-mattnowdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crypto
Source: https://github.com/mattnowdev/super-review/tree/main/skills/crypto
Command: npx skills add https://github.com/mattnowdev/super-review --skill crypto-mattnowdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps prevent real-world security failures by catching common cryptography mistakes that lead to token forgery, padding oracles, weak password storage, signature verification bypasses, and secret leakage.

Core Features & Use Cases

  • Anti-pattern detection for auth & crypto code paths: Targets risky constructs like weak RNG, IV reuse, unauthenticated encryption, JWT verification issues, and missing claim validation.
  • Evidence-driven review guidance: Provides concrete detection signals and fix directions so reviewers can quickly confirm issues in the diff.
  • Practical coverage of common developer footguns: Addresses TLS verification disabled, RSA/AES misuse, constant-time comparison requirements, key separation, and logging/redaction concerns for secrets.

Quick Start

Use the crypto skill when reviewing a PR that changes authentication, token generation, encryption/decryption, JWT handling, password hashing, or TLS-related code so the reviewer can get a focused anti-pattern checklist with prioritized fixes.

Frequently Asked Questions about crypto

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

FAQPage Schema
How do I review code for cryptography anti-patterns in a pull request?

To review code for cryptography anti-patterns, target risky constructs in authentication and encryption modules like weak RNG, IV reuse, and unauthenticated encryption. Apply evidence-driven detection signals to map issues to concrete remediation guidance for fixes.

What are common JWT verification weaknesses in application security code?

Common JWT verification weaknesses include algorithm confusion, missing kid validation, and skipped claim checks. Reviewing these token signing and verifying routines ensures strict alg/kid/claim validation to prevent signature verification bypasses and token forgery.

How do I fix password hashing parameter errors with bcrypt and Argon2?

Fix password hashing parameter errors by enforcing RFC-compliant practices for bcrypt and Argon2 configurations. Review parameter values in hashing routines to ensure they meet current security standards for strong password storage and resistance to brute-force attacks.

How do I prevent secret leakage via logs in encryption and auth modules?

Prevent secret leakage by enforcing redaction of sensitive material in logging statements within encryption, decryption, and API webhook validation modules. Review log outputs to ensure cryptographic keys and tokens are never exposed in plaintext.

Does this crypto review cover insecure TLS settings and AES-GCM misuse?

Yes, this crypto review covers insecure TLS settings and AES-GCM misuse by detecting disabled TLS verification and unauthenticated encryption. It maps these detection signals to prioritized fixes across AES-GCM/CBC modes and TLS verification requirements.

When do I need constant-time comparisons for signature validation?

Constant-time comparisons are needed whenever signature validation or API webhook verification occurs to prevent timing attacks. Enforce constant-time comparison requirements in security code review to protect against signature verification bypasses.