gmail-skill

The code implements a legitimate Gmail/Contacts client and shows no clear malware, covert data theft, persistence, or suspicious network activity. It has a significant attachment path traversal/arbitrary file-write risk, lacks OAuth state validation, stores sensitive tokens without explicit permission hardening, and does not implement the advertised send confirmation. Attachment filenames should be sanitized with a basename and containment check, OAuth state must be verified, and token files should use restrictive permissions.