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 commands/awarexone/agentic-bug-hunter/portscangit clone --depth 1 https://github.com/Awarexone/Agentic-Bug-HunterWhat 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.00000 | $0.00552 |
| Opus 5 | $0.00000 | $0.00276 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
portscan 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 3d 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.
What it actually says
/portscan
The main recon pipeline is HTTP-only (httpx / nuclei / katana), so open ports that don't speak HTTP are invisible. This maps the full service surface and pulls the interesting, often-forgotten ports to the top — the ones that turn into instant wins.
Usage
/portscan target.com # top-100 ports
/portscan target.com --top 1000
/portscan target.com -p 22,6379,27017
/portscan -l recon/target.com/subdomains/resolved.txt --json
/portscan target.com --smap # passive (Shodan) — no packets sent
Run directly:
tools/port_scanner.py target.com --top 1000
Tooling
Wraps ProjectDiscovery's naabu (fast SYN/CONNECT scan), falling back to
smap (Shodan-backed, sends no packets — handy when active scanning is out of
scope). Both are registered in tools/external_arsenal.sh. If neither is
installed the command prints install hints and exits cleanly.
What it flags
Any open, non-web port with a known attack surface, e.g.:
| Port | Service | Why it matters |
|---|---|---|
| 6379 | redis | unauth → RCE / full data dump |
| 2375 | docker | unauth Docker API → instant host RCE |
| 27017 | mongodb | unauth → database dump |
| 9200 | elasticsearch | unauth → index dump |
| 3306 / 5432 / 1433 | mysql / postgres / mssql | database exposed to the internet |
| 3389 | rdp | weak creds / BlueKeep-class |
| 445 | smb | null session / EternalBlue-class |
Web ports (80/443/8080/…) are counted but not flagged — the rest of the pipeline already covers those.
Chain
/portscan → non-web service found → pivot with the matching technique (e.g.
unauth Redis → CONFIG SET webshell, exposed DB → dump, Docker API → container
escape). Feed resolved subdomains from /recon straight in with -l.
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.
- 3d ago First seen · 57 lines · 0 tokens per session scan A 6c70ed23a521
portscan is a command published in the GitHub repository Awarexone/Agentic-Bug-Hunter (4,651 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 552 tokens. 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-30.
Other commands, from other repositories
recon
Run full recon pipeline on a target — subdomain enum (Chaos API + subfinder), live host discovery (dnsx + httpx), URL crawl (katana + waybackurls + gau), gf pattern classification, nuclei scan. Outputs to recon/ / directory. Usage: /recon target.com.
hunt
Active vulnerability hunting. Two-track dispatcher — asks Red Team vs WAPT, hands off to hunt-dispatch skill and sibling commands. Usage: /hunt target.com | /hunt .target.com | /hunt targets.txt [--vuln-class X] [--source-code P] [--chrome].
token-scan
Meme coin and token security scan — checks for rug pull vectors (hidden mint, honeypot, fee manipulation, LP lock bypass, authority retention, bonding curve exploits, fake renounce, sandwich amplification). Manual 8-class grep audit (with an optional automated scanner if present). Usage: /token-scan [--chain solana].
autopilot
Run autonomous hunt loop on a target — scope check → recon → rank surface → hunt → validate → report with configurable checkpoints. Usage: /autopilot target.com [--paranoid|--normal|--yolo].
triage
Quick 7-Question Gate triage on a finding before writing a report. Kills N/A submissions before they happen. Faster than /validate — for quick go/no-go decisions. Usage: /triage.
validate
Validate a finding — runs 7-Question Gate + 4-gate checklist. Kills weak findings before report writing. Prevents N/A submissions that hurt validity ratio. Usage: /validate.