Back to catalog
Static reviewDevelopment

Skill dossier

performing-api-inventory-and-discovery

Source declaration

Performs API inventory and discovery to identify all API endpoints in an organization's environment including documented, undocumented, shadow, zombie, and deprecated APIs. The tester uses passive traffic analysis, active scanning, DNS enumeration, JavaScript analysis, and cloud resource inventory to build a comprehensive API catalog. Maps to OWASP API9:2023 Improper Inventory Management. Activates for requests involving API discovery, shadow API detection, API inventory audit, or attack surface mapping.

The author's original description, preserved in English. It describes intent, not verified performance.

Performs API inventory and discovery to identify all API endpoints in an organization's environment including documented, undocumented, shadow, zombie, and deprecated APIs. The tester uses passive traffic analysis, active scanning, DNS enumeration, JavaScript analysis, and cloud resource inventory to build a comprehensive API catalog. Maps to OWASP API9:2023 Improper Inventory Management. Activates for requests involving API discovery, shadow API detection, API inventory audit, or attack surface mapping.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Performs API inventory and discovery to identify all API endpoints in an organization's environment including documented, undocumented, shadow, zombie, and deprecated APIs. The tester uses passive traffic analysis, active scanning, DNS enumeration, JavaScript analysis, and cloud resource inventory to build a comprehensive API catalog. Maps to OWASP API9:2023 Improper Inventory Management. Activates for requests involving API discovery, shadow API detection, API inventory audit, or attack surface mapping. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/performing-api-inventory-and-discovery/SKILL.md:L57]
  • Step 1: Passive API Discovery from Traffic Analysis [Source statement; provisional, not tested. Evidence: skills/performing-api-inventory-and-discovery/SKILL.md:L59]
  • Step 2: Active API Endpoint Discovery [Source statement; provisional, not tested. Evidence: skills/performing-api-inventory-and-discovery/SKILL.md:L127]
  • Step 3: JavaScript Source Analysis for API Endpoints [Source statement; provisional, not tested. Evidence: skills/performing-api-inventory-and-discovery/SKILL.md:L214]
  • Step 4: Cloud API Gateway Inventory [Source statement; provisional, not tested. Evidence: skills/performing-api-inventory-and-discovery/SKILL.md:L278]
  • Step 5: API Version and Shadow API Detection [Source statement; provisional, not tested. Evidence: skills/performing-api-inventory-and-discovery/SKILL.md:L331]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-api-inventory-and-discovery/SKILL.md:L1-L35]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
38.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-api-inventory-and-discovery/LICENSEOther11 KB
skills/performing-api-inventory-and-discovery/references/api-reference.mdReference2.2 KB
skills/performing-api-inventory-and-discovery/scripts/agent.pyScript8.6 KB
skills/performing-api-inventory-and-discovery/SKILL.mdInstruction16.6 KB

SKILL.md frontmatter

{
  "name": "performing-api-inventory-and-discovery",
  "description": "Performs API inventory and discovery to identify all API endpoints in an organization's environment including documented, undocumented, shadow, zombie, and deprecated APIs. The tester uses passive traffic analysis, active scanning, DNS enumeration, JavaScript analysis, and cloud resource inventory to build a comprehensive API catalog. Maps to OWASP API9:2023 Improper Inventory Management. Activates for requests involving API discovery, shadow API detection, API inventory audit, or attack surface mapping.\n",
  "domain": "cybersecurity",
  "subdomain": "api-security",
  "tags": [
    "api-security",
    "owasp",
    "api-discovery",
    "shadow-api",
    "inventory",
    "attack-surface"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.PS-01",
    "ID.RA-01",
    "PR.DS-10",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1190",
    "T1059.007",
    "T1552.001",
    "T1078.004",
    "T1530"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Passive API Discovery from Traffic Analysis

    Source-described action candidate under “Step 1: Passive API Discovery from Traffic Analysis”; not verified execution.

  4. 04
    Action

    Step 2: Active API Endpoint Discovery

    Source-described action candidate under “Step 2: Active API Endpoint Discovery”; not verified execution.

  5. 05
    Input

    Step 3: JavaScript Source Analysis for API Endpoints

    Source-described input candidate under “Step 3: JavaScript Source Analysis for API Endpoints”; not verified execution.

  6. 06
    Action

    Step 4: Cloud API Gateway Inventory

    Source-described action candidate under “Step 4: Cloud API Gateway Inventory”; not verified execution.

Inspect all extracted workflow candidates (18 candidate steps)
  1. 07
    Action

    Step 5: API Version and Shadow API Detection

    Source-described action candidate under “Step 5: API Version and Shadow API Detection”; not verified execution.

  2. 08
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  3. 09
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  4. 10
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  5. 11
    Action

    DNS enumeration discovers 340 subdomains, 45 contain API-related keywords (api, rest, gateway, backend)

    Source-described action candidate under “Scenario: Enterprise API Attack Surface Assessment”; not verified execution.

  6. 12
    Action

    Active probing of all subdomains with API path wordlist discovers 127 live API endpoints

    Source-described action candidate under “Scenario: Enterprise API Attack Surface Assessment”; not verified execution.

  7. 13
    Action

    JavaScript analysis of the main web application reveals 34 API endpoints, 8 of which point to undocumented internal services

    Source-described action candidate under “Scenario: Enterprise API Attack Surface Assessment”; not verified execution.

  8. 14
    Action

    AWS API Gateway inventory shows 67 REST APIs and 23 HTTP APIs across 12 accounts

    Source-described action candidate under “Scenario: Enterprise API Attack Surface Assessment”; not verified execution.

  9. 15
    Action

    Cross-referencing against the official API catalog: 31 shadow APIs (undocumented), 14 zombie APIs (deprecated versions)

    Source-described action candidate under “Scenario: Enterprise API Attack Surface Assessment”; not verified execution.

  10. 16
    Action

    3 zombie APIs have no authentication, exposing customer data through endpoints that were supposed to be decommissioned

    Source-described action candidate under “Scenario: Enterprise API Attack Surface Assessment”; not verified execution.

  11. 17
    Action

    2 shadow APIs expose internal admin functions to the internet without authorization

    Source-described action candidate under “Scenario: Enterprise API Attack Surface Assessment”; not verified execution.

  12. 18
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

40 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

26 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 26 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

14 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 14 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-api-inventory-and-discovery/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/performing-api-inventory-and-discovery/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-api-inventory-and-discovery
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.