Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/allsmog/blackbox-claude-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/allsmog/blackbox-claude-plugin/bb-crack)<a href="https://agentmods.dev/commands/allsmog/blackbox-claude-plugin/bb-crack"><img src="https://agentmods.dev/badge/commands/allsmog/blackbox-claude-plugin/bb-crack.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.00881 |
| Opus 5 | $0.00015 | $0.00441 |
| Sonnet 5 | $0.00006 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
bb-crack scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hash Cracking Command
Overview
Automates hash cracking workflow: identifies hash type, finds wordlists, and cracks with hashcat/john.
Workflow
Step 1: Identify Hash Type
# By length
# 32 chars = MD5 or NTLM
# 40 chars = SHA1
# 64 chars = SHA256
# By format
# $1$ = md5crypt (mode 500)
# $5$ = sha256crypt (mode 7400)
# $6$ = sha512crypt (mode 1800)
# $2a$/$2b$ = bcrypt (mode 3200)
# Using hashid
hashid '<HASH>'
hashid -m '<HASH>' # Shows hashcat mode
Step 2: Find Wordlist
# Check common locations
WORDLIST=""
for path in \
"/usr/share/wordlists/rockyou.txt" \
"/usr/share/wordlists/rockyou.txt.gz" \
"/usr/share/seclists/Passwords/Leaked-Databases/rockyou.txt" \
"$HOME/wordlists/rockyou.txt"; do
if [ -f "$path" ]; then
WORDLIST="$path"
break
fi
done
# Extract if gzipped
if [[ "$WORDLIST" == *.gz ]]; then
zcat "$WORDLIST" > /tmp/rockyou.txt
WORDLIST="/tmp/rockyou.txt"
fi
echo "Using wordlist: $WORDLIST"
Step 3: Crack with Hashcat
# Save hash to file
echo "<HASH>" > /tmp/hash.txt
# Common modes
# 0 = MD5
# 100 = SHA1
# 1000 = NTLM
# 1400 = SHA256
# 1800 = sha512crypt
# 3200 = bcrypt
hashcat -m <MODE> /tmp/hash.txt "$WORDLIST" --force -o /tmp/cracked.txt
# Check result
cat /tmp/cracked.txt
Step 4: Alternative - John
echo "<HASH>" > /tmp/hash.txt
john --wordlist="$WORDLIST" /tmp/hash.txt
john --show /tmp/hash.txt
Quick Reference
| Hash Type | Length/Format | Hashcat Mode |
|---|---|---|
| MD5 | 32 hex chars | 0 |
| SHA1 | 40 hex chars | 100 |
| SHA256 | 64 hex chars | 1400 |
| NTLM | 32 hex chars | 1000 |
| md5crypt | $1$salt$hash | 500 |
| sha512crypt | $6$salt$hash | 1800 |
| bcrypt | $2a$/$2b$/$2y$ | 3200 |
| Kerberos TGS | $krb5tgs$ | 13100 |
| AS-REP | $krb5asrep$ | 18200 |
Examples
Crack MD5
hashcat -m 0 /tmp/hash.txt /path/to/rockyou.txt --force
Crack NTLM
hashcat -m 1000 /tmp/hash.txt /path/to/rockyou.txt --force
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 125 lines · 31 tokens per session scan A 5ff6aea20dd1
bb-crack is a command published in the GitHub repository allsmog/blackbox-claude-plugin (5 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 881 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
pentest
Activate pentest mode — displays ASCII art, configures session isolation, collects engagement scope, then OWNS the engagement: pre-flight, recon, planning (via the pentester-orchestrator planner), executor dispatch, a time-budget quota loop, aggregation, and report generation.
pentest-attacks
Define the attack profile for an engagement — select which attack categories and skills to use. Saves to .pentest-attacks.json. If run before /pentest:pentest, the orchestrator will respect the selection. If run standalone, does not launch a pentest.
pentest-kali
Connect to a Metasploit-Kali Server (MKS) REST API — verifies connectivity, discovers available Kali tools, and configures agents to prefer MKS endpoints over local Bash equivalents.
pentest-scope
Define or update engagement scope — saves scope to disk without launching a pentest. Can be run before or during an engagement. If a pentest is active and the target changes drastically, warns the operator and suggests a new engagement.
pentest-exit
Close pentest session — summarizes findings, ensures outputs are saved, lifts isolation, and prompts for /clear.
unpack
Detect and remove binary packing/protection.