api-security

Installation
SKILL.md

API Security Testing (REST, GraphQL, WebSocket, SOAP)

This is the hunting counterpart of api-recon. api-recon maps the API surface and stops; this skill attacks the mapped surface under an authorized engagement. The standing finding quality gates and the adversarial gate in your system prompt apply throughout, and an access-control finding only exists once a second account or role has proven the boundary is real.

Attribution: adapted from the api-security playbook of zhaoxuya520/reverse-skill (MIT License).

Boundaries

  • Rate-limit and load tests only within the engagement's written impact budget. Most bounty programs forbid denial of service outright; volume that degrades the service for other users is out of bounds. Race-condition tests use a handful of concurrent requests, never load tools.
  • Do not exfiltrate real user data to prove a BOLA. One record you are authorized to touch, or your own second account, is sufficient evidence.
  • Destructive payloads (deletion, mass assignment on write endpoints) only against accounts and resources created for the test.
  • Every confirmed finding needs a replayable artifact: the exact request, the exact response, and the authorization context that produced it.

Phase checklists

Phase 1: discovery (handoff from api-recon)

Installs
12
Repository
baarai/artex
GitHub Stars
14.2K
First Seen
12 days ago