# API Attack Surface Mapper

> api-attack-surface-mapper

- Skill: `45ck/api-attack-surface-mapper` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 45ck/api-attack-surface-mapper`
- Raw SKILL.md: https://api.skillmd.com/api/skills/45ck/api-attack-surface-mapper/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: 45ck (https://skillmd.com/u/45ck)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/45ck/api-attack-surface-mapper

---

# api-attack-surface-mapper

## Purpose
Map the API attack surface of an authorized target by enumerating endpoints, verbs, auth paths, object relationships, and abuse opportunities.

## Trigger this skill when
- The current artifact or engagement needs a structured security-testing step rather than ad hoc probing.
- You need evidence-backed outputs that can hand off cleanly to reporting or remediation.
- You are working only within owned or explicitly authorized scope.

## Expected inputs
- API docs
- routes/endpoints
- auth model
- sample requests
- business workflows

## Deliverables
- API surface map
- endpoint inventory
- auth/authorization review points
- abuse hypotheses
- priority test targets

## Operating procedure
1. Confirm the authorization, scope, red lines, and stop conditions before doing anything else.
2. Read the artifact or engagement context from an assessor perspective and identify the highest-value review path first.
3. Prefer safe proof, minimal-impact testing, and evidence capture over deeper exploitation.
4. Separate facts, hypotheses, validated observations, and unresolved questions.
5. Record what was tested, what was not tested, and why.
6. Finish with the most sensible handoff skill based on whether the next need is more testing, reporting, or remediation.

## Quality gates
- Output remains specific to the authorized target and current evidence.
- Unsafe, out-of-scope, or ambiguous actions are explicitly rejected or escalated.
- Findings or test plans are concrete enough for another engineer or reviewer to follow.
- Recommendations are actionable and proportional to the demonstrated issue.

## Handoff targets
- parameter-pollution-checker
- manual-web-test-sequencer
- report-finding-writer

## Output style
- Be explicit about authorization assumptions and testing boundaries.
- Prefer concrete evidence paths, affected scope, and next actions over generic advice.
- Separate facts, hypotheses, validated findings, and recommendations.
- Make the output usable by defenders, builders, and reviewers.

## Failure modes to avoid
- Do not proceed as though all targets are authorized when the scope is unclear.
- Do not recommend disruptive or destructive actions when lower-impact proof is sufficient.
- Do not blur speculation and validated evidence.
- Do not produce vague findings that owners cannot reproduce or fix.

## Minimum output skeleton
```md
## Summary
## Facts and scope
## Structured outputs
## Risks or findings
## Recommendations
## Recommended next skill
```