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-recon)<a href="https://agentmods.dev/commands/allsmog/blackbox-claude-plugin/bb-recon"><img src="https://agentmods.dev/badge/commands/allsmog/blackbox-claude-plugin/bb-recon.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.00041 | $0.00983 |
| Opus 5 | $0.00020 | $0.00491 |
| Sonnet 5 | $0.00008 | $0.00197 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade B, and why
bb-recon scanned grade B with 1 finding 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 7d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo nmap -sU --top-ports 50 -oA recon/nmap_udp <TARGET> How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Reconnaissance
Overview
Performs comprehensive network reconnaissance to discover open ports, running services, and potential attack vectors.
Scan Strategy
Quick Scan (Default)
Fast discovery of common ports with service detection:
nmap -sC -sV -oA recon/nmap_quick <TARGET>
Full TCP Scan
Complete port coverage (takes longer):
nmap -p- -T4 --min-rate=1000 -oA recon/nmap_full <TARGET>
Targeted Scan
After discovering open ports, run detailed scan:
nmap -sC -sV -p<PORTS> -oA recon/nmap_targeted <TARGET>
UDP Scan
Check for UDP services (requires root):
sudo nmap -sU --top-ports 50 -oA recon/nmap_udp <TARGET>
Execution Flow
Step 1: Create Output Directory
mkdir -p recon
Step 2: Run Quick Scan
nmap -sC -sV -oA recon/nmap_quick <TARGET>
Parse output and identify:
- Open ports
- Service versions
- Script output (default NSE scripts)
- OS detection hints
Step 3: Run Full Port Scan (Background)
nmap -p- -T4 --min-rate=1000 -oA recon/nmap_full <TARGET> &
Step 4: Analyze Results
For each discovered service, note:
- Port number
- Service name
- Version information
- Any banners or additional info
Common Port Analysis
| Port | Service | Next Steps |
|---|---|---|
| 21 | FTP | Check anonymous login, version exploits |
| 22 | SSH | Banner grab, check version, brute force |
| 23 | Telnet | Check for auth bypass, credentials |
| 25 | SMTP | User enumeration, relay testing |
| 53 | DNS | Zone transfer, subdomain enum |
| 80/443 | HTTP/S | Web enumeration, nikto, gobuster |
| 110/143 | POP3/IMAP | Mail enumeration |
| 139/445 | SMB | Share enum, null session, vuln scan |
| 389/636 | LDAP | AD enumeration, anonymous bind |
| 1433 | MSSQL | Default creds, xp_cmdshell |
| 3306 | MySQL | Default creds, UDF |
| 3389 | RDP | BlueKeep, brute force |
| 5432 | PostgreSQL | Default creds |
| 5985/5986 | WinRM | Evil-WinRM access |
| 6379 | Redis | Unauth access, RCE |
| 8080 | HTTP-Alt | Web enumeration |
| 27017 | MongoDB | Unauth access |
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.
- 7d ago First seen · 149 lines · 41 tokens per session scan B b0088dcf00e2
bb-recon is a command published in the GitHub repository allsmog/blackbox-claude-plugin (5 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 983 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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-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-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-exit
Close pentest session — summarizes findings, ensures outputs are saved, lifts isolation, and prompts for /clear.
unpack
Detect and remove binary packing/protection.