api-sec

Route API security testing to the appropriate workflow based on observed endpoint signals.

2|Updated May 15, 2026
One-click install
npx skills add https://github.com/lNwNl/Methodos --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/Methodos/tree/main/docker/opencode/skills/api-sec
Command: npx skills add https://github.com/lNwNl/Methodos --skill api-sec-lnwnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

api-sec removes the guesswork of choosing the correct API security workflow by routing you to the most relevant topic based on what you observe in the target.

Core Features & Use Cases

  • API security triage routing: Selects the next testing track among API recon/docs, object authorization/BOLA, token/JWT abuse, and GraphQL/hidden parameters.
  • Observation-driven decision making: Converts concrete signals like OpenAPI/Swagger presence, authorization-relevant identifiers, JWT visibility, or /graphql endpoints into the appropriate deeper skill path.
  • Ordered exploration strategy: Recommends a practical progression from exposed endpoints and documentation to authorization boundaries, then token/rate-limit checks, and finally GraphQL/hidden-field analysis.

Quick Start

Use api-sec when you see an API target with Swagger/OpenAPI docs to decide the first deeper skill to run for API recon and documentation-based security discovery.

Frequently Asked Questions about api-sec

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

FAQPage Schema
How do I triage API security testing across different attack surfaces?

API security triaging routes your testing to the correct workflow by analyzing endpoint signals like OpenAPI docs, BOLA identifiers, or GraphQL endpoints. This observation-driven approach determines whether to pursue recon, authorization, token abuse, or hidden-parameter tracks.

What is the best way to start API security testing when Swagger or OpenAPI documentation is exposed?

Start API security testing by using exposed Swagger or OpenAPI documentation to select the first deeper skill. This routing process establishes an ordered exploration strategy, progressing from exposed endpoints to authorization boundaries and token checks.

How do I identify whether to test for BOLA or JWT abuse during API security assessments?

Identify BOLA or JWT abuse testing paths by observing object identifiers and visible tokens in requests. The triage rules map these concrete signals to the appropriate authorization or token abuse workflow before executing deeper assessments.

Does API security routing work for both REST and GraphQL testing scenarios?

API security routing works for REST, mobile backend, and GraphQL testing scenarios. It evaluates visible indicators like /graphql endpoints or hidden parameters to set the exploration order across the relevant security testing tracks.

When should I use an API security triage routing workflow?

Use an API security triage routing workflow when you need to set the exploration order for a target API. It is required when the first decision must route testing across recon, authorization, token abuse, and hidden-parameter tracks based on observed signals.