Sponsor Suno AI Music arrow_forward
Slash Command

Crypto Audit

Reviews cryptographic implementations for security vulnerabilities

Type
Slash Command
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026

What Crypto Audit is

Crypto Audit is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Crypto Audit gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Crypto Audit

Claude Code

  1. Download crypto-audit.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/packages/security-pro-pack/plugins/03-cryptography/commands/crypto-audit.md, shared under the repository's MIT license. Read the full file on GitHub.

Automatically reviews cryptographic implementations in your codebase to identify weak algorithms, improper key management, and common cryptographic vulnerabilities.

What This Command Does

Automated Crypto Code Review:

  • Detects weak or broken algorithms (MD5, SHA-1, DES, RC4)
  • Identifies insufficient key sizes (RSA <2048-bit, AES <128-bit)
  • Finds hardcoded keys and secrets
  • Checks for proper IV generation and usage
  • Verifies authenticated encryption usage
  • Validates TLS/SSL configurations

Output: Crypto audit report with severity-rated findings and remediation steps

Time: 10-20 minutes per codebase

When to Use This Command

Perfect For:

  • Pre-commit crypto review
  • Security code review automation
  • Compliance requirement (crypto standards)
  • After adding crypto functionality
  • Regular security audits

Use This When:

  • Implementing encryption or hashing
  • Reviewing third-party crypto code
  • Preparing for security audit
  • Responding to crypto vulnerabilities
  • Onboarding new crypto libraries

Usage

# Audit current directory
/crypto-audit

# Audit specific file
/crypto-audit src/crypto/encryption.js

# Audit with detailed output
/crypto-audit --verbose

# Audit and generate report
/crypto-audit --output crypto-report.md

Shortcut:

/ca  # Quick crypto audit

What Gets Audited

1. Weak Algorithms (Critical)

Detects:

  • MD5 hashing (completely broken)
  • SHA-1 hashing (collision attacks)
  • DES encryption (56-bit key, easily brute-forced)
  • RC4 stream cipher (biases in keystream)
  • ECB mode (pattern leakage)

Example Finding:

#  CRITICAL: MD5 password hashing detected
import hashlib
password_hash = hashlib.md5(password.encode()).hexdigest()

# Location: auth/password.py:45
# Severity: Critical
# CWE: CWE-327 (Use of Broken Crypto Algorithm)

# Impact: MD5 collisions can be generated in seconds
# Attacker can create password with same hash

# Remediation:
import argon2
password_hash = argon2.hash(password)

2. Insufficient Key Sizes (High)

Checks:

  • RSA key size (minimum 2048-bit, recommend 3072-bit)
  • AES key size (minimum 128-bit, recommend 256-bit)
  • Elliptic curve key size (minimum 256-bit)

Example Finding:

// ️ HIGH: RSA key size insufficient
const key = crypto.generateKeyPairSync('rsa', {
  modulusLength: 1024  // TOO SMALL! Easily factored
})

// Location: services/encryption.js:23
// Severity: High
// CWE: CWE-326 (Inadequate Encryption Strength)

// Fix: Increase to 3072-bit
const key = crypto.generateKeyPairSync('rsa', {
  modulusLength: 3072  // Secure for next 10+ years
})

3. Hardcoded Secrets (Critical)

Finds:

  • Hardcoded encryption keys
  • Embedded API keys
  • Fixed salts or IVs
  • Hardcoded passwords

Example Finding:

//  CRITICAL: Hardcoded encryption key
const ENCRYPTION_KEY = "MySecretKey123456789012345678901"

// Location: config/crypto.js:12
// Severity: Critical
// CWE: CWE-798 (Hardcoded Credentials)

// Impact: If source code leaks, all encrypted data compromised

// Fix: Use environment variables
const ENCRYPTION_KEY = process.env.ENCRYPTION_KEY
if (!ENCRYPTION_KEY) throw new Error('Missing ENCRYPTION_KEY')

4. IV/Nonce Issues (High)

Detects:

  • Reused initialization vectors
  • Predictable IVs
  • Missing IVs for CBC mode
  • Zero IVs

Example Finding:

# ️ HIGH: Fixed IV reuse
IV = b'1234567890123456'  # Same IV every time!

# Location: crypto/aes.py:34
# Severity: High
# CWE: CWE-329 (Not Using Random IV with CBC)

# Impact: Reveals patterns in encrypted data
# First block of identical plaintexts produce identical ciphertexts

# Fix: Generate random IV per encryption
IV = os.urandom(16)

5. Unauthenticated Encryption (High)

Checks for:

  • AES-CBC without HMAC
  • CTR mode without authentication
  • Missing auth tags

Example Finding:

// ️ HIGH: Encryption without authentication
const cipher = crypto.createCipheriv('aes-256-cbc', key, iv)

// Location: api/encrypt.js:56
// Severity: High
// CWE: CWE-353 (Missing Support for Integrity Check)

// Impact: Attacker can modify ciphertext without detection
// Padding oracle attacks possible

// Fix: Use GCM mode (authenticated encryption)
const cipher = crypto.createCipheriv('aes-256-gcm', key, iv)

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Crypto Audit?

Crypto Audit is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Reviews cryptographic implementations for security vulnerabilities

How do I install Crypto Audit in Claude Code?

Download crypto-audit.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Crypto Audit in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Crypto Audit safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.