codebase-hotspotsv2listed

Analyse all the source file located in the location specified by `$ARGUMENTS` in order to identify where risky processing is performed from a security perspective. ## Scope If an argument is provided in `$ARGUMENTS`, restrict the analysis to that entry point or package. Otherwise, analyze all entry points in the codebase. ## Definition All foundational concepts — **Entry point**, **Source**, **Sink**, **Data validation**, and **Risky processing** — are defined in the `# Definition` section of `.claude/skills/codebase-hotspotsv2/shared-rules.md`. Read that section before starting the analysis. ## Methodology You must follow all these steps in the defined sequence order. ### Step 1: Cartography of all the entry points * You **enumerate all entry points** using Glob/Grep (route definitions, `main()`, CLI handlers, queue consumers, exported public API functions) present into the codebase. * You must restrict codebase to `$ARGUMENTS` if provided. ### Step 2: Analysis of every entry points * An agent is dedicated to single class of vulnerability. * You must analyze all the identified entry points. * The analyze of an every entry point consist to follow the information from its **source** location to its **sink** location. * You trace the data flow, if during the flow the information reach the sink without being **validated** then you must: * Identify the corresponding dedicated agent using the **Dedicated agents registry** section below, then spawn it via `TaskCreate`.