What problem does it solve? Classical signature algorithms like RSA, ECDSA, and Ed25519 are vulnerable to future quantum attacks, leaving signed code and artifacts exposed to tampering. This Skill guides AI agents to implement NIST FIPS 204/205 post-quantum signature verification so repositories can detect code tampering and enforce fail-closed execution. ## Core Features & Use Cases - ML-DSA-65 Signing Infrastructure: Step-by-step blueprints for generating keypairs with OpenSSL 3.5+, signing files, and deploying verification scripts with git hooks. - Agent Integration Protocol: Auto-detection of public keys and signatures, structured audit logging, and fail-closed refusal when verification fails. - Secure Coding Patterns: Reference implementations for secrets redaction, path containment, parameterized subprocess spawning, and Argon2id password hashing. - Use Case: A maintainer wants to protect release artifacts against supply-chain tampering. The agent generates an ML-DSA-65 keypair, signs all distribution files, commits the public key to .pqc-keys/, and adds CI verification that rejects any artifact whose signature does not verify. ## Quick Start Ask the agent to set up ML-DSA-65 signature verification for this repository, including key generation, signing of shell scripts, and a git post-merge verification hook.