Api Recon And Docs
- 2.4k installs
- 1.5k repo stars
- Updated June 16, 2026
- yaklang/hack-skills
api-recon-and-docs is an agent skill that >-.
About
SKILL API Recon and Docs Endpoints Schemas and Version Surface AI LOAD INSTRUCTION Use this skill first when the target is a REST mobile or GraphQL API and you need to enumerate endpoints documentation versions and hidden surface area before exploitation 1 Discover all reachable API entrypoints 2 Extract schemas optional fields and role differences 3 Identify old versions mobile paths GraphQL endpoints and undocumented parameters bash curl https target app js grep oE api rest graphql sort u Common documentation and schema paths The api recon and docs agent skill provides documented workflows prerequisites triggers and safety guidance from its SKILL md source Agents load it when user requests match the description and follow step by step instructions without inventing capabilities It integrates with standard agent tooling for the tasks inputs outputs and failure modes described in the repository documentation
- API reconnaissance and documentation review playbook. Use when discovering endpoints, schemas, versions, OpenAPI specs,
- > **AI LOAD INSTRUCTION**: Use this skill first when the target is a REST, mobile, or GraphQL API and you need to enumer
- 1. Discover all reachable API entrypoints.
- Follow api-recon-and-docs SKILL.md steps and documented constraints.
- Follow api-recon-and-docs SKILL.md steps and documented constraints.
Api Recon And Docs by the numbers
- 2,404 all-time installs (skills.sh)
- +132 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #383 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
api-recon-and-docs capabilities & compatibility
- Capabilities
- api reconnaissance and documentation review play · > **ai load instruction**: use this skill first · 1. discover all reachable api entrypoints. · follow api recon and docs skill.md steps and doc
- Use cases
- orchestration
What api-recon-and-docs says it does
API reconnaissance and documentation review playbook. Use when discovering endpoints, schemas, versions, OpenAPI specs, hidden docs, and surface area for API testing.
> **AI LOAD INSTRUCTION**: Use this skill first when the target is a REST, mobile, or GraphQL API and you need to enumerate endpoints, documentation, versions, and hidden surface area before exploitat
1. Discover all reachable API entrypoints.
npx skills add https://github.com/yaklang/hack-skills --skill api-recon-and-docsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.4k |
|---|---|
| repo stars | ★ 1.5k |
| Security audit | 1 / 3 scanners passed |
| Last updated | June 16, 2026 |
| Repository | yaklang/hack-skills ↗ |
When should an agent use api-recon-and-docs and what problem does it solve?
>-
Who is it for?
Developers invoking api-recon-and-docs as documented in the skill source.
Skip if: Skip when requirements fall outside api-recon-and-docs documented scope.
When should I use this skill?
>-
What you get
Outputs aligned with the api-recon-and-docs SKILL.md workflow and stated deliverables.
- API endpoint inventory
- Schema and version map
- Discovered documentation paths
By the numbers
- Primary goals cover 3 discovery targets: entrypoints, schemas with role differences, and version or mobile path surface
Files
SKILL: API Recon and Docs — Endpoints, Schemas, and Version Surface
AI LOAD INSTRUCTION: Use this skill first when the target is a REST, mobile, or GraphQL API and you need to enumerate endpoints, documentation, versions, and hidden surface area before exploitation.
1. PRIMARY GOALS
1. Discover all reachable API entrypoints. 2. Extract schemas, optional fields, and role differences. 3. Identify old versions, mobile paths, GraphQL endpoints, and undocumented parameters.
2. RECON CHECKLIST
JavaScript and client mining
curl https://target/app.js | grep -oE '(/api|/rest|/graphql)[^"'\'' ]+' | sort -uCommon documentation and schema paths
/swagger.json
/openapi.json
/api-docs
/docs
/.well-known/
/graphql
/gqlVersion and product drift
/api/v1/
/api/v2/
/api/mobile/v1/
/legacy/3. WHAT TO EXTRACT FROM DOCS
- optional and undocumented fields
- admin-only request examples
- deprecated endpoints that may still be active
- schema hints like
additionalProperties: true - parameter names tied to filtering, sorting, IDs, roles, or tenancy
4. NEXT ROUTING
| Finding | Next Skill |
|---|---|
| object IDs everywhere | api authorization and bola |
| JWT, OAuth, role claims | api auth and jwt abuse |
| GraphQL or hidden fields | graphql and hidden parameters |
| strong auth boundary but suspicious business flow | business logic vulnerabilities |
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Choose api-recon-and-docs over generic HTTP probing skills when structured schema and documentation extraction is required before security testing.
FAQ
What is api-recon-and-docs?
>-
When should I use api-recon-and-docs?
>-
Is api-recon-and-docs safe to install?
Review the Security Audits panel on this page before production use.