Skip to main content
command CX Codex

surface — Claude Code command: what it does, how to install

Shows a ranked attack surface for a target from its recon manifest and hunt memory.

MIT ★ 16,193 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add elementalsouls/Claude-BugHunter
/plugin install claude-bughunter@elementalsouls
Open on GitHub

What surface does

The command reads the manifest at recon/<target>/manifest.json produced by cbh recon and memory of previously tested endpoints. It layers signal from engine/skill_map.py (surface → bug class → skill mapping) and outputs three lists: P1 (start here), P2 (after P1), and Kill List (skip). The deterministic ranking comes from cbh surface <target>.

It prints endpoints with tech stacks, first-seen dates, and suggested test vectors (IDOR, auth bypass, file upload). If no recon data exists, the command prompts you to run /recon target.com first.

What it helps with

  • get a prioritized list of endpoints to test for vulnerabilities
  • see how attack surface maps to bug classes and skills
  • filter out endpoints not worth testing

Example prompts for the agent

  • Show attack surface for example.com
  • Run /claude-bughunter:surface api.target.io
  • List ranked endpoints for shop.example.org

How to install surface

1Plugin marketplace

/plugin marketplace add elementalsouls/Claude-BugHunter
/plugin install claude-bughunter@elementalsouls

2Manually: put the files in place

.claude/commands/surface.md

Call it with /surface. For all projects use ~/.claude/commands/

Questions about surface

How to install surface in Claude Code?

Run /plugin marketplace add elementalsouls/Claude-BugHunter, then /plugin install claude-bughunter@elementalsouls. The command will be at .claude/commands/surface.md.

What does the surface command do?

It reads the target's recon manifest and hunt memory, ranks endpoints by priority, and outputs three lists: P1 (start here), P2 (after P1), and Kill List (skip).

What does surface need to work?

Run /recon target.com first to create the manifest at recon/<target>/manifest.json. Without it, the command will prompt you to run recon.

Source text

surface.md · MIT
---
name: surface
description: Show ranked attack surface for a target from its recon manifest + hunt memory. Deterministic backing is `cbh surface <target>` (reads recon/<target>/manifest.json); LLM layer adds ledger signal. Usage: /surface target.com
---

# /surface

View the prioritized attack surface for a target.

## What This Does

1. Reads the recon manifest at `recon/<target>/manifest.json` (produced by `cbh recon`)
   — the deterministic ranking comes from `cbh surface <target>`
2. Reads hunt memory for patterns and previously tested endpoints
3. Layers `engine/skill_map.py` (surface → bug-class → skill) + ledger signal on
   top of the manifest's `ranked_surface` (P1/P2/Kill)
4. Outputs P1 (start here), P2 (after P1), and Kill List (skip)

> The manifest is the recon→hunt contract — see [`docs/recon-manifest.md`](../docs/recon-manifest.md).
> Run `cbh surface <target>` for the raw deterministic ranking.

## 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
```

© Sachin Sharma · MIT · elementalsouls/Claude-BugHunter

Similar slash commands

All slash commands for Security →

From the same set92

The whole set →
offensive-osint The offensive-osint skill gives Claude Code technical references for external reconnaissance, from subdomain discovery to secret triage. Use it for authorized red-team or bug-bounty work. CX Codex +1 ★ 16,193repo stars remember remember — a slash command to manually add a note to a bug report or target system. The automatic capture during autopilot runs works on its own; this is for details the engine would miss. CX Codex +1 ★ 16,193repo stars pickup pickup pulls previous target recon from the Claude-BugHunter ledger to inspect tested endpoints, tech stack, and confirmed findings. CX Codex +1 ★ 16,193repo stars memory-gc The memory-gc command checks the autopilot’s JSONL ledgers and rotates files that exceed a size cap. Use it when findings.jsonl or negatives.jsonl keeps growing. CX Codex +1 ★ 16,193repo stars intel Fetches target intelligence on demand: scans NVD and GitHub advisories, checks HackerOne reports, and flags untested endpoints from hunt memory. CX Codex +1 ★ 16,193repo stars scope scope is a Claude Code command that checks hosts and URLs before active testing. It blocks assets outside engagement rules during security work. CX Codex +1 ★ 16,193repo stars hunt-exceptional-conditions The hunt-exceptional-conditions skill reveals when an app leaks stack traces, server paths, or library versions through unhandled exceptions triggered by malformed input. Effective for testing APIs and web endpoints. CX Codex +1 ★ 16,193repo stars triage triage evaluates security findings through a 7-question gate before you write a bug report. It helps bug bounty hunters discard invalid submissions immediately. CX Codex +1 ★ 16,193repo stars

Project sponsors

Companies that keep this analytics open