surface

A command that ranks the most relevant attack points for a security-testing target, such as a website or API. It uses saved reconnaissance results and previous testing notes to group findings into priorities and a skip list.

In plain words
What is it for?
Run `/surface target.com` after reconnaissance to review priority endpoints, suggested tests, related past patterns, and areas to skip.
Why use it?
It prevents testers from working through endpoints in an arbitrary order. The ranking highlights promising areas first and records which parts are unlikely to be useful.

Command

Install

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.

agentmods
npx agentmods add commands/awarexone/agentic-bug-hunter/surface
Clone the repo
git clone --depth 1 https://github.com/Awarexone/Agentic-Bug-Hunter
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 342 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00342
Opus 5 $0.00000 $0.00171
Sonnet 5 $0.00000 $0.00068
Haiku 4.5 $0.00000 $0.00034

Measured 2d ago against content hash c8218a007bc7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

surface 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 2d 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.

commands/surface.md · 52 lines

What it actually says

/surface

View the prioritized attack surface for a target.

What This Does

  1. Reads cached recon output from recon/<target>/
  2. Reads hunt memory for patterns and previously tested endpoints
  3. Invokes the recon-ranker agent to produce a prioritized ranking
  4. Outputs P1 (start here), P2 (after P1), and Kill List (skip)

Usage

/surface target.com

Prerequisites

Run /recon target.com first. If no recon data exists, you'll be prompted to run recon.

Output

ATTACK SURFACE: target.com
═══════════════════════════════════════

Priority 1 (start here):
1. api.target.com/v2/users/{id} — IDOR candidate
   Tech: Express + PostgreSQL | First seen 12 days ago
   Suggested: numeric ID swap on GET/PUT/DELETE

2. api.target.com/graphql — introspection enabled, 47 mutations
   Suggested: field-level auth check on sensitive mutations

Priority 2 (after P1):
1. cdn.target.com:8443/upload — file upload endpoint
   Suggested: extension bypass, magic bytes

Kill List (skip):
- static.target.com — CDN only
- docs.target.com — third-party hosted

Memory:
- Pattern from alpha.com (same tech): auth bypass via method override ($800)
- 3 endpoints tested in previous session, 5 remain
Changes

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.

  1. 2d ago First seen · 52 lines · 0 tokens per session scan A c8218a007bc7

Subscribe to this mod's changes

surface is a command published in the GitHub repository Awarexone/Agentic-Bug-Hunter (4,651 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 342 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.

Related

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.

elementalsouls/Claude-BugHunter · 65 tokens

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].

elementalsouls/Claude-BugHunter · 63 tokens

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].

elementalsouls/Claude-BugHunter · 79 tokens

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].

elementalsouls/Claude-BugHunter · 49 tokens

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.

elementalsouls/Claude-BugHunter · 41 tokens

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.

elementalsouls/Claude-BugHunter · 45 tokens