jsanalyzer

# JsAnalyzer **Orchestrator-based JS security analysis.** Primary context delegates all heavy work to specialized agents. --- ## Architecture: Orchestrator Pattern ``` PRIMARY CONTEXT (Light Orchestrator) │ ├── Phase 1-3: Spawn in PARALLEL │ ├── js-grep-analyzer (haiku) → paths, endpoints │ ├── js-tool-runner (haiku) → doctorswzl output │ └── js-architecture-analyzer (opus) → architecture docs │ ├── Phase 4: Spawn in PARALLEL │ ├── source-sink-tracer (opus) × N │ ├── postmessage-analyzer (opus) × N │ ├── api-investigator (opus) × N │ └── secrets-analyzer (opus) × 1 │ └── Phase 5: Synthesize (light) ``` **Primary context NEVER:** - Runs greps directly - Parses JSON output - Reads large files for analysis **Primary context ONLY:** - Spawns agents - Waits for results (TaskOutput) - Creates final summary reports --- ## Workflow Routing | Trigger | Workflow | Action | |---------|----------|--------| | `/js-analyze <domain>` or `/jsa <domain>` | LiveSite.md | Acquire from live site → FullScan | | `/js-analyze` (in folder with .js files) | FullScan.md | All 5 phases with agents | | "analyze js files" | Analyze.md | Phases 1-3 only | | "review findings" | Review.md | Phases 4-5 only | **Note:** If given a domain/URL, use LiveSite workflow. If in a folder with JS files, use FullScan. --- ## Execution **When triggered, IMMEDIATELY:** 1. Read workflow: `${PAI_DIR}/skills/JsAnalyzer/workflows/FullScan.md` 2. Execute the orchestrator pattern as specified 3....