crypto

Detect and remediate weak cryptography while implementing secure controls across services.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill crypto-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crypto
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/crypto
Command: npx skills add https://github.com/arbazkhan971/godmode --skill crypto-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams identify, remediate, and implement correct cryptographic controls so applications do not use weak algorithms, mishandle keys, or misconfigure TLS, reducing the risk of data breaches and compliance failures.

Core Features & Use Cases

  • Algorithm guidance: Recommends secure choices such as Argon2id for passwords, AES-256-GCM or ChaCha20-Poly1305 for symmetric encryption, and Ed25519 for signatures.
  • Practical patterns: Prescribes envelope encryption, KMS-backed key storage and rotation, nonce/IV safety, and JWT/TLS hardening checks.
  • Use Case: Audit a web service to replace deprecated hashes, enforce Argon2id for auth, rotate signing keys, and upgrade TLS to 1.2+.

Quick Start

Request a full cryptographic audit and remediation plan for your repository, including password hashing, encryption-at-rest, JWT validation, and TLS configuration.

Frequently Asked Questions about crypto

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

FAQPage Schema
How do I audit my application code for weak cryptography and deprecated hashing algorithms?

To audit weak cryptography, request a full cryptographic audit and remediation plan for your repository to detect deprecated hashes, enforce modern algorithms like Argon2id, and upgrade TLS to 1.2+.

What is the best way to implement secure password hashing and encryption at rest?

The best way to implement secure password hashing and encryption is by applying prescribed patterns like Argon2id for passwords, AES-256-GCM or ChaCha20-Poly1305 for symmetric encryption, and envelope encryption for data at rest.

How does KMS-backed key management and rotation work for securing APIs?

KMS-backed key management secures APIs by enforcing a safe key lifecycle, utilizing KMS-backed key storage and rotation, and hardening JWT signing to prevent unauthorized access and compliance failures.

Can I use this to harden TLS configuration and enforce TLS 1.2+ across my deployment environments?

Yes, you can harden TLS configuration across services and deployment environments by enforcing TLS 1.2+ checks, upgrading misconfigured deployments, and flagging deprecated cryptographic primitives.

When should I use envelope encryption and nonce safety checks for my infrastructure?

You should implement envelope encryption and nonce safety checks when applying secure cryptographic controls across repositories and infrastructure to prevent data breaches and ensure proper key lifecycle management.

What cryptographic controls are enforced to prevent JWT misconfiguration and key mishandling?

Cryptographic controls enforced include JWT validation hardening, Ed25519 for signatures, KMS-backed key storage, and strict nonce/IV safety to prevent key mishandling and reduce breach risks.