api-sec

Routes API security testing into recon, authorization, token abuse, and GraphQL workflows.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/lNwNl/Praxis --skill api-sec-lnwnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-sec
Source: https://github.com/lNwNl/Praxis/tree/main/skills/api-sec
Command: npx skills add https://github.com/lNwNl/Praxis --skill api-sec-lnwnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting API security testing, it is hard to decide which attack surface to investigate first. This Skill acts as an entry-point router that classifies the observed API behavior and directs you to the correct deeper testing workflow. ## Core Features & Use Cases - Category Routing: Classifies API findings into four tracks: recon/docs, object authorization (BOLA/BFLA), JWT/token abuse, and GraphQL/hidden parameters. - Quick Triage Table: Maps concrete observations (Swagger presence, IDs in URLs, JWTs in traffic, /graphql endpoints) to the right specialized skill. - Recommended Testing Order: Suggests a sequence from endpoint discovery through authorization, token boundaries, and schema abuse. - Use Case: During a web penetration test you discover a REST API with JWT authentication and a /graphql endpoint. Use this Skill to decide whether to start with API recon, BOLA testing, or GraphQL introspection. ## Quick Start Use the api-sec skill to triage this API target and tell me which API security testing workflow to start with.

Frequently Asked Questions about api-sec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start API security testing on a new target?▼

Start by identifying what the API exposes: Swagger or OpenAPI docs, object IDs in URLs or JSON, JWT tokens in traffic, or GraphQL endpoints. Each observation maps to a specific testing track such as recon, BOLA authorization checks, token abuse, or schema abuse.

What is BOLA and when should I test for it?▼

BOLA (Broken Object Level Authorization) occurs when APIs expose object IDs without verifying user ownership. Test for it whenever IDs appear in URLs, JSON bodies, headers, or GraphQL arguments by substituting other users' identifiers.

How do I test JWT tokens in API traffic?▼

When a JWT appears in API traffic, route to token abuse testing: examine header trust, claim manipulation, signature validation, and rate-limit bypass. The api-auth-and-jwt-abuse workflow covers these checks.

Does this skill perform the actual API attacks?▼

No, it is a routing entry point only. It classifies observations and points to deeper topic skills like api-recon-and-docs, api-authorization-and-bola, api-auth-and-jwt-abuse, and graphql-and-hidden-parameters that contain the detailed procedures.

When should GraphQL testing take priority over REST API testing?▼

Prioritize GraphQL testing when a /graphql endpoint or batched JSON arrays are present. Introspection, batching abuse, and undocumented fields require dedicated techniques that differ from standard REST authorization checks.