ginskill-init 1.0.0

package/skills/review-code/scripts/run-review.sh

@@ -0,0 +1,167 @@
+#!/usr/bin/env bash
+# ─────────────────────────────────────────────────────────────
+# Code Review — Automated Checks
+#
+# Runs ESLint, TypeScript type-check, and test suite against
+# the specified target (backend, frontend, or both).
+# Auto-detects project directories from the repo root.
+#
+# Usage:
+#   ./run-review.sh backend          # lint + test backend only
+#   ./run-review.sh frontend         # lint + type-check + test frontend only
+#   ./run-review.sh all              # both
+#   ./run-review.sh backend --fix    # auto-fix lint issues
+#
+# Environment variables (override auto-detection):
+#   BE_DIR=./my-backend  FE_DIR=./my-frontend  ./run-review.sh all
+#
+# Output: JSON report at ./review-output/review-report.json
+# ─────────────────────────────────────────────────────────────
+
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+REPO_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || cd "$SCRIPT_DIR/../../../../.." && pwd)"
+
+# ─── Auto-detect project directories ─────────────────────────
+detect_dir() {
+  local kind="$1"
+  shift
+  for candidate in "$@"; do
+    if [ -d "$REPO_ROOT/$candidate" ] && [ -f "$REPO_ROOT/$candidate/package.json" ]; then
+      echo "$REPO_ROOT/$candidate"
+      return
+    fi
+  done
+  echo ""
+}
+
+BE_DIR="${BE_DIR:-$(detect_dir backend backend be-* server api apps/api apps/backend)}"
+FE_DIR="${FE_DIR:-$(detect_dir frontend frontend web-* client apps/web apps/frontend)}"
+
+OUTPUT_DIR="$SCRIPT_DIR/../review-output"
+REPORT="$OUTPUT_DIR/review-report.json"
+
+TARGET="${1:-all}"
+FIX_FLAG="${2:-}"
+
+mkdir -p "$OUTPUT_DIR"
+
+# ─── Helpers ─────────────────────────────────────────────────
+log()  { echo "  [review] $*"; }
+warn() { echo "  [warn]   $*"; }
+ok()   { echo "  [ok]     $*"; }
+fail() { echo "  [fail]   $*"; }
+
+run_check() {
+  local name="$1"
+  local dir="$2"
+  shift 2
+  local cmd=("$@")
+
+  log "Running $name..."
+  local start_ms
+  start_ms=$(date +%s%3N 2>/dev/null || date +%s)
+
+  local output exit_code=0
+  output=$( cd "$dir" && "${cmd[@]}" 2>&1 ) || exit_code=$?
+
+  local end_ms
+  end_ms=$(date +%s%3N 2>/dev/null || date +%s)
+  local duration_ms=$(( end_ms - start_ms ))
+
+  if [ $exit_code -eq 0 ]; then
+    ok "$name passed (${duration_ms}ms)"
+  else
+    fail "$name failed (exit $exit_code, ${duration_ms}ms)"
+  fi
+
+  # Append to results array
+  RESULTS+=("{\"check\":\"$name\",\"exit_code\":$exit_code,\"duration_ms\":$duration_ms,\"output\":$(echo "$output" | head -100 | python3 -c 'import json,sys; print(json.dumps(sys.stdin.read()))' 2>/dev/null || echo '""')}")
+}
+
+RESULTS=()
+
+# ─── Backend Checks ──────────────────────────────────────────
+if [[ "$TARGET" == "backend" || "$TARGET" == "all" ]]; then
+  log ""
+  if [ -z "$BE_DIR" ]; then
+    warn "No backend directory detected — set BE_DIR or ensure a backend/ directory exists"
+  else
+    log "═══ Backend ($(basename "$BE_DIR")) ═══"
+
+    if [ -d "$BE_DIR/node_modules" ]; then
+      if [[ "$FIX_FLAG" == "--fix" ]]; then
+        run_check "backend-lint-fix" "$BE_DIR" npx eslint "{src,apps,libs,test}/**/*.ts" --fix
+      else
+        run_check "backend-lint" "$BE_DIR" npx eslint "{src,apps,libs,test}/**/*.ts" --max-warnings 50
+      fi
+
+      run_check "backend-test" "$BE_DIR" npx jest --config jest.config.cjs --passWithNoTests --silent
+    else
+      warn "Backend node_modules not found — run 'npm install' in $(basename "$BE_DIR")/ first"
+      RESULTS+=("{\"check\":\"backend-deps\",\"exit_code\":1,\"duration_ms\":0,\"output\":\"node_modules not found\"}")
+    fi
+  fi
+fi
+
+# ─── Frontend Checks ─────────────────────────────────────────
+if [[ "$TARGET" == "frontend" || "$TARGET" == "all" ]]; then
+  log ""
+  if [ -z "$FE_DIR" ]; then
+    warn "No frontend directory detected — set FE_DIR or ensure a frontend/ directory exists"
+  else
+    log "═══ Frontend ($(basename "$FE_DIR")) ═══"
+
+    if [ -d "$FE_DIR/node_modules" ]; then
+      if [[ "$FIX_FLAG" == "--fix" ]]; then
+        run_check "frontend-lint-fix" "$FE_DIR" npx next lint --fix
+      else
+        run_check "frontend-lint" "$FE_DIR" npx next lint
+      fi
+
+      run_check "frontend-typecheck" "$FE_DIR" npx tsc --noEmit
+
+      run_check "frontend-test" "$FE_DIR" npx jest --passWithNoTests --silent
+    else
+      warn "Frontend node_modules not found — run 'npm install' in $(basename "$FE_DIR")/ first"
+      RESULTS+=("{\"check\":\"frontend-deps\",\"exit_code\":1,\"duration_ms\":0,\"output\":\"node_modules not found\"}")
+    fi
+  fi
+fi
+
+# ─── Generate Report ─────────────────────────────────────────
+log ""
+log "═══ Generating Report ═══"
+
+RESULTS_JSON=$(printf '%s\n' "${RESULTS[@]}" | paste -sd ',' -)
+cat > "$REPORT" <<EOF
+{
+  "timestamp": "$(date -u +%Y-%m-%dT%H:%M:%SZ)",
+  "target": "$TARGET",
+  "repo_root": "$REPO_ROOT",
+  "checks": [$RESULTS_JSON]
+}
+EOF
+
+ok "Report saved to $REPORT"
+
+# ─── Summary ─────────────────────────────────────────────────
+TOTAL=${#RESULTS[@]}
+PASSED=0
+for r in "${RESULTS[@]}"; do
+  if echo "$r" | grep -q '"exit_code":0'; then
+    PASSED=$((PASSED + 1))
+  fi
+done
+FAILED=$((TOTAL - PASSED))
+
+log ""
+log "════════════════════════════════"
+log "  Results: $PASSED/$TOTAL passed"
+if [ $FAILED -gt 0 ]; then
+  fail "  $FAILED check(s) failed"
+  exit 1
+else
+  ok "  All checks passed!"
+fi

package/skills/review-code/scripts/scan-codebase.sh

@@ -0,0 +1,152 @@
+#!/usr/bin/env bash
+# ─────────────────────────────────────────────────────────────
+# Codebase Scanner
+#
+# Quick scan of the entire monorepo for common code quality
+# issues. Auto-detects project directories.
+#
+# Usage:
+#   ./scan-codebase.sh              # scan everything
+#   ./scan-codebase.sh --json       # output as JSON
+#
+# Environment variables (override auto-detection):
+#   BE_SRC=./my-backend/src  FE_SRC=./my-frontend/src  ./scan-codebase.sh
+# ─────────────────────────────────────────────────────────────
+
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+REPO_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || cd "$SCRIPT_DIR/../../../../.." && pwd)"
+
+# ─── Auto-detect project directories ─────────────────────────
+detect_src() {
+  local kind="$1"
+  shift
+  for candidate in "$@"; do
+    if [ -d "$REPO_ROOT/$candidate/src" ]; then
+      echo "$REPO_ROOT/$candidate/src"
+      return
+    fi
+  done
+  echo ""
+}
+
+BE_SRC="${BE_SRC:-$(detect_src backend backend be-* server api apps/api apps/backend)}"
+FE_SRC="${FE_SRC:-$(detect_src frontend frontend web-* client apps/web apps/frontend)}"
+
+JSON_MODE="${1:-}"
+
+echo ""
+echo "  ╔══════════════════════════════════════════╗"
+echo "  ║  Codebase Scanner                         ║"
+echo "  ╚══════════════════════════════════════════╝"
+echo ""
+
+# ─── Backend Scan ─────────────────────────────────────────────
+if [ -n "$BE_SRC" ] && [ -d "$BE_SRC" ]; then
+  BE_NAME="$(basename "$(dirname "$BE_SRC")")"
+  echo "  ═══ Backend ($BE_NAME) ═══"
+  echo ""
+
+  # Count features
+  FEATURE_COUNT=$(ls -1d "$BE_SRC/features"/*/ 2>/dev/null | wc -l | tr -d ' ')
+  echo "  Feature modules: $FEATURE_COUNT"
+
+  # Total TS files
+  BE_TS_COUNT=$(find "$BE_SRC" -name "*.ts" | wc -l | tr -d ' ')
+  echo "  TypeScript files: $BE_TS_COUNT"
+
+  # Test files
+  BE_TEST_COUNT=$(find "$BE_SRC" -name "*.spec.ts" -o -name "*.test.ts" 2>/dev/null | wc -l | tr -d ' ')
+  echo "  Test files: $BE_TEST_COUNT"
+
+  # Test coverage ratio
+  if [ "$BE_TS_COUNT" -gt 0 ]; then
+    COVERAGE_PCT=$(( BE_TEST_COUNT * 100 / BE_TS_COUNT ))
+    echo "  Test file ratio: ${COVERAGE_PCT}%"
+  fi
+
+  echo ""
+  echo "  Code quality indicators:"
+
+  # any usage across backend
+  ANY_COUNT=$(grep -r ": any\b" "$BE_SRC" --include="*.ts" 2>/dev/null | wc -l | tr -d ' ')
+  echo "    'any' type usage: $ANY_COUNT occurrences"
+
+  # TODO/FIXME/HACK comments
+  TODO_COUNT=$(grep -ri "TODO\|FIXME\|HACK\|XXX" "$BE_SRC" --include="*.ts" 2>/dev/null | wc -l | tr -d ' ')
+  echo "    TODO/FIXME/HACK: $TODO_COUNT comments"
+
+  # console.log (should use structured logger)
+  CONSOLE_COUNT=$(grep -r "console\.log\|console\.error\|console\.warn" "$BE_SRC" --include="*.ts" 2>/dev/null | wc -l | tr -d ' ')
+  echo "    console.* usage: $CONSOLE_COUNT (should use structured logger)"
+
+  # Empty catch blocks
+  EMPTY_CATCH=$(grep -r "catch.*{" "$BE_SRC" --include="*.ts" -A1 2>/dev/null | grep -c "^[[:space:]]*}" || true)
+  echo "    Potentially empty catch blocks: $EMPTY_CATCH"
+
+  # Modules without tests
+  echo ""
+  echo "  Modules without tests:"
+  for mod_dir in "$BE_SRC/features"/*/; do
+    mod_name=$(basename "$mod_dir")
+    test_files=$(find "$mod_dir" -name "*.spec.ts" -o -name "*.test.ts" 2>/dev/null | wc -l | tr -d ' ')
+    if [ "$test_files" -eq 0 ]; then
+      echo "    - $mod_name"
+    fi
+  done
+
+  # Modules without Swagger docs
+  echo ""
+  echo "  Modules without Swagger decorators:"
+  for mod_dir in "$BE_SRC/features"/*/; do
+    mod_name=$(basename "$mod_dir")
+    swagger=$(grep -r "@ApiTags\|@ApiOperation" "$mod_dir" 2>/dev/null | wc -l | tr -d ' ')
+    controller=$(find "$mod_dir" -name "*.controller.ts" 2>/dev/null | wc -l | tr -d ' ')
+    if [ "$controller" -gt 0 ] && [ "$swagger" -eq 0 ]; then
+      echo "    - $mod_name"
+    fi
+  done
+
+  # Top any-heavy files
+  echo ""
+  echo "  Top 10 files by 'any' usage:"
+  grep -rc ": any\b" "$BE_SRC" --include="*.ts" 2>/dev/null | grep -v ":0$" | sort -t: -k2 -rn | head -10 | while IFS=: read -r file count; do
+    echo "    $count  ${file#$REPO_ROOT/}"
+  done
+else
+  echo "  [skip] No backend source directory detected"
+fi
+
+# ─── Frontend Scan ────────────────────────────────────────────
+echo ""
+if [ -n "$FE_SRC" ] && [ -d "$FE_SRC" ]; then
+  FE_NAME="$(basename "$(dirname "$FE_SRC")")"
+  echo "  ═══ Frontend ($FE_NAME) ═══"
+  echo ""
+
+  FE_TS_COUNT=$(find "$FE_SRC" -name "*.ts" -o -name "*.tsx" | wc -l | tr -d ' ')
+  echo "  TypeScript files: $FE_TS_COUNT"
+
+  FE_TEST_COUNT=$(find "$FE_SRC" -name "*.spec.ts" -o -name "*.spec.tsx" -o -name "*.test.ts" -o -name "*.test.tsx" 2>/dev/null | wc -l | tr -d ' ')
+  echo "  Test files: $FE_TEST_COUNT"
+
+  # use client directives
+  USE_CLIENT=$(grep -rl "\"use client\"" "$FE_SRC" --include="*.tsx" --include="*.ts" 2>/dev/null | wc -l | tr -d ' ')
+  echo "  'use client' components: $USE_CLIENT"
+
+  # any usage
+  FE_ANY=$(grep -r ": any\b" "$FE_SRC" --include="*.ts" --include="*.tsx" 2>/dev/null | wc -l | tr -d ' ')
+  echo "  'any' type usage: $FE_ANY"
+
+  # console usage
+  FE_CONSOLE=$(grep -r "console\.log" "$FE_SRC" --include="*.ts" --include="*.tsx" 2>/dev/null | wc -l | tr -d ' ')
+  echo "  console.log usage: $FE_CONSOLE"
+else
+  echo "  [skip] No frontend source directory detected"
+fi
+
+echo ""
+echo "  ════════════════════════════════════════════"
+echo "  Scan complete."
+echo ""

package/skills/security-scanner/SKILL.md

@@ -0,0 +1,327 @@
+---
+name: security-scanner
+description: |
+  **Security Scanner**: Comprehensive security audit for fullstack monorepos — NestJS backend, Next.js frontend, and React Native mobile app. Aligned with OWASP Top 10:2025, OWASP Top 10 for LLM Apps 2025, and OWASP Mobile Top 10. Scans for vulnerabilities, secrets exposure, auth misconfigurations, injection risks, supply chain threats, LLM/AI agent risks, and platform-specific security issues.
+  - MANDATORY TRIGGERS: security scan, security audit, security review, check security, vulnerability scan, find vulnerabilities, check secrets, secret leak, hardcoded password, hardcoded key, OWASP, injection, XSS, CSRF, auth security, token security, check dependencies, dependency audit, CVE, security headers, CORS check, CSP check, penetration test, pen test, security checklist, supply chain, prompt injection, LLM security
+  - Use this skill whenever the user mentions anything about security, vulnerabilities, secrets, or wants to audit code for safety issues. Also trigger when the user asks about CORS, CSP headers, auth guards, token handling, API key exposure, dependency vulnerabilities, supply chain risks, prompt injection, or AI agent security — even casual mentions like "is this secure?" or "any security issues?".
+---
+
+# Security Scanner
+
+Scan fullstack monorepos for security vulnerabilities with deep awareness of the project's architecture. Aligned with **OWASP Top 10:2025**, **OWASP Top 10 for LLM Applications 2025**, and **OWASP Mobile Top 10 2024**. This skill understands modern NestJS/Next.js/React Native security posture.
+
+## Project Security Architecture (Current State)
+
+### What's Already Good
+- JWT with 15min access / 7d refresh tokens (`core/config/jwt.config.ts`)
+- Global `ValidationPipe` with `whitelist: true` + `forbidNonWhitelisted: true`
+- Mobile uses `react-native-keychain` (OS-level secure storage, not AsyncStorage)
+- Single-flight token refresh pattern prevents race conditions
+- Swagger protected with basic auth middleware
+- HSTS enabled (1 year, preload)
+- Signed httpOnly cookies for token transport
+
+### Known Risks (Flagged)
+- CSP allows `'unsafe-inline'` in both `scriptSrc` and `styleSrc`
+- `connectSrc: ["'self'", 'https://*']` — too permissive
+- CORS defaults to `['*']` in non-production environments
+- `.env.example` may contain reusable example secrets
+- `strictNullChecks: false` increases null-related vulnerability surface
+
+## OWASP Alignment
+
+### OWASP Top 10:2025 — Web Application Risks
+Map every finding to these categories where applicable:
+
+| ID | Category | What to Check |
+|----|----------|---------------------|
+| A01 | Broken Access Control | IDOR in user endpoints, auth guard gaps, RBAC bypass |
+| A02 | Security Misconfiguration | CORS wildcard, CSP unsafe-inline, Helmet config |
+| A03 | Software Supply Chain Failures | npm dependencies, lockfile integrity, lifecycle scripts |
+| A04 | Cryptographic Failures | JWT signing, token storage, TLS configuration |
+| A05 | Injection | NoSQL injection (MongoDB), XSS, command injection |
+| A06 | Insecure Design | Missing rate limiting, no abuse detection on AI endpoints |
+| A07 | Authentication Failures | Token handling, refresh flow, session management |
+| A08 | Software/Data Integrity Failures | CI/CD pipeline, unsigned OTA updates, unverified deps |
+| A09 | Security Logging & Alerting | Missing audit logs, no alerting on suspicious activity |
+| A10 | Mishandling Exceptional Conditions | Uncaught errors leaking stack traces, fail-open patterns |
+
+### OWASP Top 10 for LLM Applications 2025
+The project uses LangChain + LangGraph agents with multi-provider LLMs — these risks are critical:
+
+| ID | Category | Check |
+|----|----------|-------|
+| LLM01 | Prompt Injection | User input sanitized before LLM prompts? System prompts hidden? |
+| LLM02 | Sensitive Info Disclosure | PII leaked in LLM responses? Conversation history access controlled? |
+| LLM03 | Supply Chain | LLM package versions pinned? Model provenance verified? |
+| LLM05 | Improper Output Handling | AI-generated content sanitized before rendering/storing? |
+| LLM06 | Excessive Agency | LangGraph tools sandboxed? Permissions scoped to minimum? |
+| LLM07 | System Prompt Leakage | System prompts retrievable by users? |
+| LLM08 | Vector/Embedding Weaknesses | Qdrant access controlled? Embedding poisoning possible? |
+| LLM10 | Unbounded Consumption | Token limits on AI calls? Rate limiting on AI endpoints? |
+
+### OWASP Mobile Top 10 2024
+For React Native (mobile app):
+
+| ID | Category | Check |
+|----|----------|-------|
+| M1 | Improper Credential Usage | Keychain used? No hardcoded credentials? |
+| M2 | Inadequate Supply Chain | Third-party SDK audit? Dependency scanning? |
+| M3 | Insecure Auth/AuthZ | Token rotation? Biometric for sensitive actions? |
+| M4 | Insufficient Input/Output Validation | Deep link params validated? WebView input sanitized? |
+| M5 | Insecure Communication | Certificate pinning? No cleartext traffic? |
+| M8 | Security Misconfiguration | Debug flags stripped? ProGuard enabled? |
+| M9 | Insecure Data Storage | AsyncStorage audit? Sensitive data encrypted? |
+| M10 | Insufficient Cryptography | Proper key management? Strong algorithms? |
+
+## Scan Process
+
+When asked to scan, follow this order. Adapt scope based on what the user asks — they might want a full audit or just one area.
+
+### 1. Determine Scope
+
+Ask (or infer) what they want scanned:
+- **Full audit** — All platforms, all categories
+- **Backend only** — NestJS auth, injection, config, dependencies
+- **Frontend only** — Next.js XSS, auth, API routes
+- **Mobile only** — React Native storage, certificate pinning, deep links
+- **Specific area** — Just auth, just secrets, just dependencies, etc.
+
+### 2. Run Automated Checks
+
+Use the scripts in `scripts/` to get quick automated results first:
+
+```bash
+# Full security scan (all platforms)
+./scripts/security-scan.sh all
+
+# Platform-specific
+./scripts/security-scan.sh backend
+./scripts/security-scan.sh frontend
+./scripts/security-scan.sh mobile
+```
+
+The script checks for: hardcoded secrets, `any` type abuse, console.log of sensitive data, missing auth guards, unsafe eval, dependency vulnerabilities, and more.
+
+### 3. Manual Review by Category
+
+After automated checks, do targeted manual review based on findings.
+
+#### Category 1: Secrets & Credentials (CRITICAL)
+
+Scan for leaked secrets, hardcoded keys, and exposed credentials.
+
+**What to look for:**
+- API keys, tokens, passwords in source code (not `.env`)
+- Secrets in `.env.example` that look real (not placeholder-ish)
+- Private keys committed to git
+- Secrets logged to console or error responses
+- Secrets in URL query parameters
+- Secrets in frontend bundles (anything prefixed `NEXT_PUBLIC_` or `EXPO_PUBLIC_`)
+
+**Known locations in this project:**
+- Check for hardcoded API keys in utility scripts and lib files
+- `.env.example` — check for example passwords that could be reused
+- `core/config/` — check all config files load from env, not hardcoded
+
+**Patterns to grep:**
+```bash
+# Hardcoded secrets
+grep -rn "password\s*[:=]\s*['\"]" --include="*.ts" --include="*.mjs"
+grep -rn "api[_-]?key\s*[:=]\s*['\"]" --include="*.ts" --include="*.mjs"
+grep -rn "secret\s*[:=]\s*['\"]" --include="*.ts"
+grep -rn "Bearer\s" --include="*.ts" --include="*.mjs"
+
+# Secrets in logs
+grep -rn "console\.log.*token\|console\.log.*password\|console\.log.*secret" --include="*.ts"
+```
+
+#### Category 2: Authentication & Authorization
+
+**Backend (NestJS):**
+- Are all non-public endpoints guarded with `@UseGuards(JwtAuthGuard)`?
+- Do user-specific queries filter by `userId` from `@CurrentUser()`?
+- Can users access/modify other users' data? (IDOR)
+- Is the admin bypass in `roles.guard.ts` properly restricted?
+- Are refresh tokens properly invalidated on logout?
+- Token expiration: are access/refresh token lifetimes enforced?
+
+**Frontend (Next.js):**
+- Are API routes in `src/app/api/` checking auth before processing?
+- Are tokens stored in httpOnly cookies (not localStorage)?
+- Is there CSRF protection on state-changing requests?
+
+**Mobile (React Native):**
+- Tokens stored in Keychain/Keystore via `react-native-keychain`? (currently yes)
+- Is biometric auth implemented for sensitive actions?
+- Are deep link handlers validating the source?
+
+Read `references/auth-security.md` for detailed checklist.
+
+#### Category 3: Injection Attacks
+
+**NoSQL Injection (MongoDB):**
+- Are Mongoose queries using user input directly in `$where`, `$regex`, or `$expr`?
+- Is `JSON.parse()` used on user input without validation?
+- Does `forbidNonWhitelisted: true` catch all inputs? (check file uploads, query params)
+
+**XSS:**
+- Is user-generated content rendered with `dangerouslySetInnerHTML`?
+- Are Markdown/rich text inputs sanitized before storage and display?
+- Do AI-generated responses get sanitized before rendering?
+
+**Command Injection:**
+- Does any code use `exec()`, `spawn()`, or `eval()` with user input?
+- Playwright scraper — is the URL validated before navigation?
+
+#### Category 4: Security Headers & CORS
+
+**Current config** (`core/config/helmet.config.ts` and `cors.config.ts`):
+
+Check these against best practices:
+- CSP should NOT have `'unsafe-inline'` (currently does)
+- `connectSrc` should list specific domains, not `https://*`
+- CORS should not default to `['*']` even in development
+- X-Frame-Options: should be `DENY` or `SAMEORIGIN`
+- Referrer-Policy: should be `strict-origin-when-cross-origin`
+
+Read `references/headers-checklist.md` for the full checklist.
+
+#### Category 5: Dependencies & Supply Chain (OWASP A03:2025)
+
+This is newly elevated in OWASP 2025. Treat supply chain as a first-class risk.
+
+```bash
+# Vulnerability scan
+cd <backend-dir> && npm audit
+cd <frontend-dir> && npm audit
+cd <mobile-dir> && npm audit
+
+# Verify package signatures (npm 9+)
+npm audit signatures
+
+# Check for lifecycle scripts that download code
+./scripts/security-scan.sh supply-chain
+```
+
+**What to check:**
+- Known CVEs in dependencies (`npm audit`)
+- Lockfile integrity — are lockfiles committed? (`pnpm-lock.yaml`, `package-lock.json`)
+- Lifecycle scripts — `preinstall`/`postinstall` that download or execute code
+- Typosquatting — dependency names close to popular packages
+- Dependency signature verification (`npm audit signatures`)
+- SBOM generation for compliance (`npm sbom --sbom-format cyclonedx`)
+- NestJS-specific: **CVE-2025-54782** — RCE in `@nestjs/devtools-integration` ≤0.2.0 (unsafe `vm.runInNewContext` + missing CORS). Verify version ≥0.2.1
+
+**Supply chain attack awareness:**
+- The Sept 2025 "Shai-Hulud" attack compromised 18 popular npm packages (chalk, debug, etc.)
+- Always disable lifecycle scripts by default: `npm config set ignore-scripts true`
+- Use `--ignore-scripts` in CI/CD and explicitly allow-list needed scripts
+
+#### Category 6: LLM/AI Agent Security (OWASP LLM Top 10)
+
+The project has LangChain + LangGraph agents, multi-provider LLMs, and Qdrant vector DB. This category is critical.
+
+**Prompt Injection (LLM01):**
+- Is user input concatenated directly into LLM prompts?
+- Are system prompts retrievable via conversation manipulation?
+- Check `features/ai-agents/` for prompt construction patterns
+- Multi-modal inputs (images) can contain hidden prompts
+
+**Output Handling (LLM05):**
+- Are AI-generated responses sanitized before rendering in frontend/mobile?
+- Can AI output contain executable HTML/JS/markdown that bypasses sanitization?
+- Are AI-suggested actions validated before execution?
+
+**Excessive Agency (LLM06):**
+- What tools can LangGraph agents call? Are they scoped to minimum permissions?
+- Can agents access/modify resources beyond the current user's scope?
+- Is there human-in-the-loop for destructive agent actions?
+
+**Vector DB Security (LLM08):**
+- Is Qdrant access authenticated?
+- Can users poison the fashion knowledge base via injected content?
+- Are embeddings isolated per tenant?
+
+**Resource Limits (LLM10):**
+- Token limits on LLM API calls?
+- Rate limiting on AI chat endpoints?
+- Timeout on LangGraph agent execution?
+
+Read `references/nestjs-security.md` → "LLM/AI Agent Security" for detailed checklist.
+
+#### Category 7: Platform-Specific
+
+Read the platform-specific references for deeper checks:
+- `references/nestjs-security.md` — Backend: auth, injection, rate limiting, error handling, LLM security
+- `references/react-native-security.md` — Mobile: OWASP Mobile Top 10, secure storage, cert pinning, binary protection
+- `references/nextjs-security.md` — Frontend: server/client boundary, API routes, CSP, dependency safety
+
+#### Category 8: Exceptional Conditions (OWASP A10:2025)
+
+New in OWASP 2025 — check how the app handles edge cases:
+- Do uncaught exceptions expose stack traces in production?
+- Do auth failures fail-open (grant access) instead of fail-closed (deny)?
+- Are Bull queue job failures handled gracefully without data loss?
+- Do LLM API timeouts fall back safely (no infinite retries, no credential exposure)?
+- Are MongoDB connection failures handled without crashing the process?
+
+### 4. Report Findings
+
+Structure the report by severity:
+
+```
+🔴 CRITICAL — Exploitable now, data at risk
+🟠 HIGH — Significant risk, should fix before next release
+🟡 MEDIUM — Defense-in-depth improvement
+🟢 LOW — Best practice recommendation
+ℹ️ INFO — Observation, no action needed
+```
+
+For each finding:
+```
+**[SEVERITY] Title**
+Location: file:line
+Impact: What an attacker could do
+Evidence: The vulnerable code
+Fix: Concrete remediation with code example
+```
+
+### 5. Provide Fix Priority
+
+End with a prioritized action list:
+1. Critical fixes (do today)
+2. High fixes (this sprint)
+3. Medium fixes (next sprint)
+4. Low/info (backlog)
+
+## Recommended Tools Integration
+
+For CI/CD pipeline integration, recommend these tools:
+
+| Tool | Type | Use Case |
+|------|------|----------|
+| **Semgrep** | SAST | Custom rules for NestJS/Next.js patterns, free for open source |
+| **npm audit** | SCA | Built-in dependency vulnerability scanning |
+| **Socket.dev** | SCA+ | Detects malicious packages, supply chain attacks |
+| **OWASP ZAP** | DAST | Runtime API scanning in staging |
+| **SonarQube** | SAST | Continuous code quality + security |
+| **Snyk** | SCA | Dependency monitoring with auto-fix PRs |
+| **Gitleaks** | Secrets | Pre-commit hook for secret detection |
+
+**AI-generated code note:** If the team uses AI coding assistants (Copilot, Claude, etc.), treat AI-generated code with the same scrutiny as external dependencies. Studies show ~40% of AI-generated security-sensitive code contains vulnerabilities.
+
+## References
+
+Platform-specific deep-dive checklists — read these when scanning a specific area:
+
+- `references/nestjs-security.md` — Backend: auth guards, injection, rate limiting, file upload, error handling, LLM/AI agent security
+- `references/react-native-security.md` — Mobile: OWASP Mobile Top 10, secure storage, certificate pinning, binary protection, deep links
+- `references/nextjs-security.md` — Frontend: server/client boundary, API routes, middleware auth, env vars, CSP, dependency supply chain
+
+**External references:**
+- [OWASP Top 10:2025](https://owasp.org/Top10/2025/)
+- [OWASP Top 10 for LLM Applications 2025](https://genai.owasp.org/llm-top-10/)
+- [OWASP Mobile Top 10](https://owasp.org/www-project-mobile-top-10/)
+- [NPM Security Cheat Sheet (OWASP)](https://cheatsheetseries.owasp.org/cheatsheets/NPM_Security_Cheat_Sheet.html)
+- [NestJS Security Best Practices](https://dev.to/drbenzene/best-security-implementation-practices-in-nestjs-a-comprehensive-guide-2p88)