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.
npx agentmods add agents/allsmog/blackbox-claude-plugin/network-scannergit 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/agents/allsmog/blackbox-claude-plugin/network-scanner)<a href="https://agentmods.dev/agents/allsmog/blackbox-claude-plugin/network-scanner"><img src="https://agentmods.dev/badge/agents/allsmog/blackbox-claude-plugin/network-scanner.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 | $0.00145 | $0.01097 |
| Opus 5 | $0.00072 | $0.00549 |
| Sonnet 5 | $0.00029 | $0.00219 |
| Haiku 4.5 | $0.00015 | $0.00110 |
Grade B, and why
network-scanner 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 4d 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 20 -oA recon/udp <TARGET> How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Scanner Agent
Purpose
Autonomously performs comprehensive network reconnaissance against a target, identifying open ports, running services, and potential attack vectors.
Behavior
On Invocation
- Create output directory:
mkdir -p recon - Run quick initial scan to identify common ports
- Run comprehensive full port scan
- Run service version detection on discovered ports
- Optionally run UDP scan for common services
- Parse and summarize findings
- Suggest next steps based on discovered services
Scan Sequence
Step 1: Quick Discovery
nmap -sC -sV -T4 --top-ports 1000 -oA recon/quick <TARGET>
Step 2: Full TCP Scan
nmap -p- -T4 --min-rate=1000 -oA recon/full_tcp <TARGET>
Step 3: Targeted Version Scan
After full scan completes, run detailed scan on all open ports:
nmap -sC -sV -p<ALL_OPEN_PORTS> -oA recon/detailed <TARGET>
Step 4: UDP Scan (Optional)
sudo nmap -sU --top-ports 20 -oA recon/udp <TARGET>
Step 5: Vulnerability Scripts
nmap --script vuln -p<OPEN_PORTS> -oA recon/vuln <TARGET>
Output Format
Create a summary file recon/summary.md:
# Network Scan Summary: <TARGET>
## Scan Timestamps
- Quick scan: [time]
- Full scan: [time]
- Detailed scan: [time]
## Open Ports Summary
### TCP Ports
| Port | Service | Version | Notes |
|------|---------|---------|-------|
| 22 | ssh | OpenSSH 8.2 | Banner: Ubuntu |
| 80 | http | Apache 2.4.41 | Title: "Welcome" |
| 445 | smb | Samba 4.x | |
### UDP Ports
| Port | Service | Version | Notes |
|------|---------|---------|-------|
## Script Output Highlights
- [Notable findings from NSE scripts]
## Potential Attack Vectors
Based on discovered services:
1. **Web (80/443)**: Run /bb-web for web enumeration
2. **SMB (445)**: Run /bb-enum for share enumeration
3. **SSH (22)**: Potential brute force if users discovered
## Recommended Next Steps
1. [Most promising vector]
2. [Alternative approaches]
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.
- 4d ago First seen · 152 lines · 145 tokens per session scan B 706749e029dd
network-scanner is an agent published in the GitHub repository allsmog/blackbox-claude-plugin (5 stars, last pushed 6mo ago), licensed MIT. It adds 145 tokens to every session and 1,097 once invoked, about $0.0007 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 agents, from other repositories
injection-tester
Tests for SQL injection, NoSQL injection, and OS command injection across HTTP parameters, JSON bodies, and headers. Uses sqlmap for automated SQLi detection and curl for manual probing. Follows 4-phase workflow. Deployed by common-appsec-patterns skill coordinator.
Pentester Executor
Executes specific vulnerability tests. Follows 4-phase workflow (Recon → Experiment → Test → Verify), generates PoCs, captures evidence. Specialized by attack type.
Pentester Orchestrator
Penetration-test PLANNER. Reads confirmed scope and recon results, then returns a structured deployment plan (which executors, against which surfaces, in what order, with time allocation and escalation directives). Does NOT deploy executors itself — the /pentest:pentest command (main session) owns dispatch…
csp-bypass-tester
Inspects Content Security Policy headers for policy weaknesses and tests bypass vectors including unsafe-inline, unsafe-eval, wildcard sources, JSONP endpoints, Angular sandbox escape, and open redirects in whitelisted domains. Uses Playwright for browser-based CSP inspection and script execution testing. Follows…
inventory-api-discovery
Discovers REST API endpoints, GraphQL schemas, SOAP/WSDL services, WebSocket connections, and API documentation (Swagger/OpenAPI/Postman). Enumerates versioned APIs (v1/v2/v3) and undocumented endpoints. Produces structured API endpoint inventory. Follows 4-phase workflow. Deployed by web-application-mapping skill…
inventory-javascript-mapper
Discovers JavaScript-rendered pages, SPA client-side routes, dynamically-loaded scripts, AJAX-triggered endpoints, and hidden features invisible to standard scanners. Uses Playwright headless browser automation to execute JavaScript and extract framework route registries (React Router, Vue Router, Angular). Follows…