crypto-source-auditlisted

# Crypto Source Audit Finding a dangerous pattern is the mechanical step. The real work is proving that a **secret** reaches it and that no mitigation breaks the chain. A grep hit with no traced secret is not a finding, and reporting one as a vulnerability is the primary failure mode of this skill. ## When to Use - Reviewing an implementation of a cipher, MAC, KDF, signature scheme, or KEM. - Auditing key, nonce, IV, PSK, or password handling anywhere in a codebase. - Reviewing TLS/handshake, token verification, or session-key derivation code. - A reviewer asks whether a function is constant-time, whether a comparison is safe, or whether a secret buffer is actually erased. - Preparing the worklist that `binary-crypto-verify` will confirm in the binary. ## When NOT to Use - **Confirming the compiler preserved a guarantee.** Source review cannot prove that a wipe survived dead-store elimination or that a select stayed branchless. Use `binary-crypto-verify` on the compiled artifact. - **Measuring timing empirically.** This skill reasons about code, not clocks. Use dudect or ctgrind for statistical leakage testing. - **General vulnerability hunting** (injection, authz, memory safety). Use `codebase-security-audit`. - **Protocol design review.** This skill audits an implementation against its intended design, not the soundness of the design itself. ## Rationalizations to Reject | Rationalization | Why it is wrong | Required action | | --- | --- | --- | | "The co