api-recon-and-docs

Enumerate API endpoints, schemas, and undocumented parameters for security testing.

2|Updated May 15, 2026
One-click install
npx skills add https://github.com/lNwNl/Methodos --skill api-recon-and-docs-lnwnl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-recon-and-docs
Source: https://github.com/lNwNl/Methodos/tree/main/docker/opencode/skills/api-recon-and-docs
Command: npx skills add https://github.com/lNwNl/Methodos --skill api-recon-and-docs-lnwnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly identify what an API exposes so you can plan accurate testing based on real endpoints, schemas, versions, and undocumented parameters.

Core Features & Use Cases

  • Endpoint and surface discovery: Finds reachable API entrypoints via client mining and common documentation routes.
  • Schema and parameter extraction: Extracts optional/undocumented fields, admin-only examples, and likely filtering/sorting/tenant parameters.
  • Version and drift detection: Surfaces legacy paths and product drift across API versions, including mobile and GraphQL routes.

Quick Start

Use this skill to enumerate API endpoints and schemas from a target domain and produce a short list of what to test next for authorization, parsing, and business-flow weaknesses.

Frequently Asked Questions about api-recon-and-docs

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

FAQPage Schema
How do I discover undocumented API endpoints and hidden parameters for security testing?

You can find hidden API documentation by analyzing client assets and probing common OpenAPI, Swagger, and GraphQL URL paths, which reveals schemas, admin-only examples, and undocumented filtering or sorting parameters.

How do I extract OpenAPI and GraphQL schemas from a target domain?

Extract OpenAPI and GraphQL schemas by enumerating reachable API entrypoints and common documentation routes, then parsing the discovered specifications to pull optional fields, examples, and schema hints like additionalProperties.

Can this skill detect API version drift across REST and mobile endpoints?

Yes, API version drift detection works across REST, mobile, and GraphQL targets by mapping legacy paths and surfacing product drift across multiple API versions during the endpoint enumeration process.

What's the best way to map an API surface before testing authorization weaknesses?

Mapping an API surface before authorization testing requires enumerating reachable entrypoints, extracting schemas and undocumented parameters, and producing a prioritized list of endpoints to test for business-flow weaknesses.

Do I need special dependencies to perform GraphQL and REST endpoint discovery?

No special dependencies are required to perform GraphQL and REST endpoint discovery, as the skill operates independently to analyze target domains and extract schema hints without external component installations.