The Complete Production SOP: How to Deploy and Run John the Ripper Password Hash Strength Auditor in Autonomous AI Agents
Step-by-step SOP to install and run John the Ripper Password Hash Strength Auditor in Codex, Claude Code, and Cursor. Includes verified prompts and fixes.
Technical Overview & Architectural Context
Autonomous coding agents frequently make critical procedural errors when tasked with security audits and credential verification. Left to their own devices, agents often hallucinate hash algorithm formats, execute unconstrained brute-force loops that exhaust CPU and memory budgets, or expose plaintext hashes directly in unredacted conversation context. Without strict sandboxing and deterministic procedures, agents may also mistakenly invoke external network utilities or write unencrypted cracked credentials to publicly accessible workspace repositories. The 'john-the-ripper-password-auditor' skill establishes rigid operational guardrails for John the Ripper (JtR) execution. It forces agents to follow strict hash format verification, wordlist restrictions, and pre-configured mangling rules before launching local attacks. By constraining filesystem permissions strictly to workspace boundaries and preventing outbound network access, this skill ensures that auditing tasks—such as benchmark evaluations, bcrypt resilience testing, and dictionary mangling—remain safe, reproducible, and compliant with enterprise security standards.
Prerequisites & Environment Requirements
Verified Search Intents & Long-Tail Queries Solved
This operational tutorial is engineered to provide deterministic solutions for these developer search queries:
Step-by-Step Execution Playbook
Local Environment Setup & SKILL.md Mounting
Create the local skill manifest directory and inject verified procedural rules into the agent runtime path.
Autonomous runtimes such as Claude Code, Cursor, and Codex automatically scan user and project directories for SKILL.md files. To configure John the Ripper auditing, install the skill file in the target agent directory so the runtime can index its YAML frontmatter, triggers, and execution SOP.
mkdir -p .agents/skills/john-the-ripper-password-auditor && curl -fsSL https://askills.dev/api/skills/john-the-ripper-password-auditor/raw -o .agents/skills/john-the-ripper-password-auditor/SKILL.md---
name: "john-the-ripper-password-auditor"
description: "Audit stored password hash strength and detect weak user credentials with John the Ripper."
metadata:
author: "openwall"
version: "1.0.0"
runtime_compatibility:
- "codex"
- "claude-code"
- "cursor"
- "windsurf"
triggers:
- "audit password hashes john"
- "crack weak password hash john"
- "benchmark john the ripper"
permissions:
fs_read: true
fs_write: "workspace"
shell_exec: false
net_access: false
---
# John the Ripper Password Hash Strength Auditor
Performs password hash auditing using John the Ripper: dictionary attacks, wordlist mangling rules, hybrid mask attacks, benchmark mode, and verifying bcrypt/sha512crypt resilience.
## When to Invoke
Invoke this skill whenever you need to:
- audit password hashes john
- crack weak password hash john
- benchmark john the ripper
## Execution SOP & Rules
1. Execute john --format=<format> --wordlist=passwords.txt hashes.txt on authorized audit dumps.
2. Apply standard wordlist mangling rules using --rules to simulate common user mutations.
3. Inspect cracked weak passwords with john --show hashes.txt to quantify policy compliance.
4. Require users with cracked weak passwords to reset credentials to strong passphrases.
## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.Keep the audit hash files scoped to a dedicated ./audit/ directory and exclude cracked wordlists from git tracking via .gitignore to minimize token exposure and prevent accidental leaks.
The skill specifies shell_exec: false and net_access: false. Any commands to execute John the Ripper must be approved via explicit agent execution prompts or run via local pre-orchestrated workspace test hooks.
Environment Secrets & Dependency Validation
Validate John the Ripper installation and prepare dictionary wordlists within the workspace.
Ensure the system contains a functional John the Ripper binary capable of detecting supported cryptographic formats (sha512crypt, bcrypt, raw-md5, raw-sha256). Verify that password dictionary fixtures are present without contaminating agent context.
which john && john --list=formats | grep -E 'bcrypt|sha512crypt' && test -f ./audit/wordlist.txt || echo 'rockyou-sample' > ./audit/wordlist.txtStore large target wordlists outside the context repository and reference them via absolute or workspace paths instead of piping raw wordlist text into chat prompts.
Do not pass unmasked production database shadow files directly. Extract only salted hash fields without personally identifiable emails or names into a dedicated audit target file.
Intent Matching & Trigger Invocation
Trigger deterministic execution using the verified frontmatter trigger phrases.
Agent runtimes match incoming user prompts against the triggers defined in the SKILL.md. Use the exact intent phrases such as 'audit password hashes john' to invoke the step-by-step auditing SOP without open-ended reasoning loops.
Explicitly state the hash format (e.g., bcrypt, sha512crypt) and duration limit in the prompt to ensure the agent selects the right parameters immediately.
Omitting the wordlist parameter may cause the agent to invoke John in default incremental mode, locking the process into high CPU utilization indefinitely.
Verification, Linting & Output Quality Gate
Inspect cracked credentials via john --show and verify remediation reporting without leaking cleartext credentials.
Once John the Ripper completes the dictionary and mangling passes, inspect the potfile results using the --show flag. The agent must summarize statistical metrics (e.g., percentage cracked, weak pattern frequency) rather than logging cleartext credentials into open log files.
john --show --format=sha512crypt ./audit/hashes.txt | tee ./audit/audit-report.logAutomate a summary parsing script that reports only hash count, cracked count, and policy compliance percentage to conserve context tokens.
Always clear or secure ~/.john/john.pot if working in shared or multi-tenant agent execution runner environments.
Real-World Scenario: Audit User Account Hashes for Weak Credentials Prior to Production Migration
“Run john-the-ripper-password-auditor: audit password hashes john in ./audit/user_hashes.txt using wordlist ./audit/wordlist.txt and format sha512crypt. Apply standard mangling rules and summarize vulnerability stats.”
Runtime Troubleshooting & Failure Modes
Root Cause: The hash dump contains syntax errors, unescaped salt delimiters, or the agent specified an incorrect --format flag incompatible with the cipher type.
head -n 5 ./audit/user_hashes.txt && john --format=dynamic_auto --show ./audit/user_hashes.txt || sed -i 's/^[ \t]*//' ./audit/user_hashes.txtRoot Cause: The autonomous agent runner is executing under a restricted container or sandboxed workspace user that lacks read/write permissions to the default user home directory.
export JOHN_HOME="$PWD/.john" && mkdir -p "$PWD/.john" && john --pot="$PWD/.john/john.pot" --wordlist=./audit/wordlist.txt ./audit/user_hashes.txtFrequently Asked Questions (John the Ripper Password Hash Strength Auditor SOP)
Q:Can I use John the Ripper Password Hash Strength Auditor across Codex, Claude Code, and Cursor simultaneously?
Yes. The skill conforms to the universal SKILL.md specification. Placing it in your workspace under .agents/skills/john-the-ripper-password-auditor/SKILL.md allows Codex, Claude Code, Cursor, and Windsurf to consume the triggers and SOP boundaries identically.
Q:How does John the Ripper Password Hash Strength Auditor prevent context window overflow during long agent sessions?
The skill enforces targeted execution flags (specific --wordlist, --rules, and --format constraints) and directs output evaluation via 'john --show' rather than printing full terminal brute-force logs into the LLM conversation window.
Q:Does this skill require escalated root or container permissions?
No. John the Ripper can execute entirely within user-space binaries using workspace-scoped wordlists and custom potfiles. The skill retains a security score of 98/100 by disabling arbitrary shell scripts and network access.
Ready to equip your autonomous agent with John the Ripper Password Hash Strength Auditor?
Copy the complete audited SKILL.md specification or download the 1-click zip bundle directly from our verified registry.