@cubis/foundry 0.3.30 → 0.3.32

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-functions/SKILL.md

@@ -1,71 +0,0 @@
----
-name: vercel-functions
-description: "Vercel Serverless and Edge Functions: core patterns, Node.js and Python runtimes, edge runtime, Fluid Compute for long-running tasks, and function configuration."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, serverless, functions, edge function, nodejs runtime, python runtime, fluid compute, function config, api route, edge runtime
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nodejs-best-practices, fastapi-expert, vercel-routing, vercel-caching
-  consolidates: vercel-functions-core, vercel-functions-edge-runtime, vercel-functions-nodejs, vercel-functions-python, vercel-function-config, vercel-fluid-compute
----
-
-# Vercel Functions
-
-## Purpose
-Design and implement Vercel Serverless and Edge Functions with the correct runtime selection, configuration, and compute strategy for each use case.
-
-## When To Use
-- Writing Vercel API routes or serverless function handlers.
-- Choosing between Edge Runtime and Node.js runtime.
-- Configuring Python serverless functions on Vercel.
-- Implementing long-running tasks or streaming with Fluid Compute.
-- Tuning function memory, regions, timeout, and concurrency config.
-
-## Domain Areas
-
-### Core Patterns
-- Request/response handler structure for Vercel functions.
-- Environment-aware error handling and status codes.
-- Cold start mitigation strategies.
-
-### Node.js Runtime
-- Use `@vercel/node` and standard Node.js APIs.
-- Streaming responses with `Response` and `ReadableStream`.
-
-### Python Runtime
-- Configure `requirements.txt` and handler conventions.
-- Use WSGI/ASGI adapters where needed.
-
-### Edge Runtime
-- Use Web Standard APIs only (no Node.js built-ins).
-- Optimize for global low-latency execution at the edge.
-- Middleware-friendly patterns.
-
-### Fluid Compute
-- Enable for long-running tasks exceeding standard limits.
-- Stream output progressively for large responses.
-- Configure max duration and concurrency appropriately.
-
-### Function Config (`vercel.json`)
-- Set `runtime`, `regions`, `maxDuration`, `memory` per function.
-- Use `rewrites` to map routes to specific functions.
-
-## Operating Checklist
-1. Choose runtime (Edge vs Node.js vs Python) based on latency, API, and duration needs.
-2. Set explicit `maxDuration` and `memory` for non-default requirements.
-3. Implement structured error responses with proper HTTP status codes.
-4. Test cold-start behavior and streaming in staging environment.
-5. Validate regional deployment targets match latency requirements.
-6. Run regression checks before promoting to production.
-
-## Output Contract
-- Runtime selection rationale and tradeoffs
-- Handler implementation with error handling and streaming
-- `vercel.json` function config section
-- Performance validation (cold start, p99 latency targets)
-- Residual risks and follow-up actions

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-observability/SKILL.md

@@ -1,87 +0,0 @@
----
-name: vercel-observability
-description: "Vercel observability stack: logs, tracing (OTel), session tracing, speed insights, web analytics, alerts, custom events, log drains, audit logs, and structured monitoring."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, observability, runtime logs, tracing, opentelemetry, session tracing, speed insights, web analytics, alerts, log drain, audit log, custom events, monitoring
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: monitoring-expert, sre-engineer, vercel-functions, vercel-firewall
-  consolidates: vercel-observability-overview, vercel-alerts-monitoring, vercel-runtime-logs, vercel-log-drain-reference, vercel-log-trace-correlation, vercel-session-tracing, vercel-tracing-otel, vercel-speed-insights, vercel-web-analytics, vercel-custom-events, vercel-audit-logs, vercel-drains-setup
----
-
-# Vercel Observability
-
-## Purpose
-Instrument, collect, and act on observability signals from Vercel deployments: structured runtime logs, distributed traces, session tracing, performance metrics, analytics, and audit events.
-
-## When To Use
-- Setting up runtime log viewing and structured log queries.
-- Configuring log drains to export to external systems (Datadog, Baselime, etc.).
-- Implementing OpenTelemetry (OTel) tracing in Vercel functions.
-- Correlating logs with traces and requests via trace IDs.
-- Monitoring Core Web Vitals with Speed Insights.
-- Collecting custom business events for product analytics.
-- Tracking user sessions for debugging with Session Tracing.
-- Reviewing audit logs for security and compliance.
-- Setting up threshold alerts on function errors, p99 latency, etc.
-
-## Domain Areas
-
-### Runtime Logs
-- View and filter logs in Vercel dashboard or CLI.
-- Structure logs with consistent fields (level, traceId, userId).
-
-### Log Drains
-- Configure HTTP or HTTPS log drain endpoints.
-- Filter by source (functions, edge, build) and log level.
-- Validate drain delivery and handle backpressure.
-
-### OpenTelemetry Tracing
-- Instrument functions with `@vercel/otel` or standard OTel SDK.
-- Export spans to Vercel or external OTLP endpoints.
-- Correlate log entries with trace IDs for unified debugging.
-
-### Session Tracing
-- Enable session capture for replay-based debugging.
-- Scope to error sessions or specific user segments.
-
-### Speed Insights
-- Install `@vercel/speed-insights` in Next.js or other frameworks.
-- Monitor LCP, FID/INP, CLS per route.
-- Set performance budgets and track regressions.
-
-### Web Analytics
-- Enable Vercel Web Analytics for privacy-first traffic data.
-- Track page views, referrers, and custom events.
-
-### Custom Events
-- Emit custom events via `@vercel/analytics/react` or REST API.
-- Use for funnel tracking, feature adoption, and error reporting.
-
-### Alerts & Monitoring
-- Configure threshold alerts on error rate, latency, and availability.
-- Route alerts to Slack, PagerDuty, or webhooks.
-
-### Audit Logs
-- Review deployment, permission, and configuration changes.
-- Export audit logs for compliance reporting.
-
-## Operating Checklist
-1. Enable runtime logs and configure structured log format.
-2. Set up log drain to external system if needed.
-3. Instrument functions with OTel and validate trace export.
-4. Install Speed Insights and establish performance budgets.
-5. Configure alerts with non-noisy thresholds and on-call routing.
-6. Schedule audit log review cadence for security compliance.
-
-## Output Contract
-- Observability architecture diagram (logs → traces → metrics → alerts)
-- Log structure schema and drain configuration
-- OTel instrumentation code and exporter config
-- Speed Insights dashboard and performance budget definition
-- Alert policy with thresholds and escalation routing

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-platform/SKILL.md

@@ -1,108 +0,0 @@
----
-name: vercel-platform
-description: "Vercel platform operations: project configuration, RBAC, 2FA/OIDC/SSO, secure compute, REST API, SDK, webhooks, integrations, MCP for agents, image optimization, OG images, cron jobs, monorepos, microfrontends, and multi-tenant architecture."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, project config, rbac, 2fa, oidc, sso, secure compute, rest api, vercel sdk, webhooks, integrations marketplace, mcp for agents, image optimization, og image, cron jobs, monorepo, microfrontends, multi-tenant, automation, audit
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: devops-engineer, secure-code-guardian, monitoring-expert, vercel-deployments, vercel-observability
-  consolidates: vercel-automation, vercel-project-configuration, vercel-rbac-access-groups, vercel-2fa-enforcement, vercel-oidc-federation, vercel-secure-compute, vercel-rest-api, vercel-sdk, vercel-webhooks-and-checks, vercel-integrations-native, vercel-marketplace-partner-api, vercel-mcp-for-agents, vercel-agent-workflows, vercel-image-optimization, vercel-og-image-generation, vercel-cron-jobs, vercel-microfrontends, vercel-monorepos, vercel-multi-tenant
----
-
-# Vercel Platform
-
-## Purpose
-Administer Vercel at the platform level — project configuration, team access control, identity/SSO, secure networking, REST API automation, webhooks, native integrations, architecture patterns (monorepos, microfrontends, multi-tenant), and platform-level features like image optimization, OG image generation, and cron jobs.
-
-## When To Use
-- Configuring project-level settings in `vercel.json`.
-- Managing team RBAC roles and access groups.
-- Enforcing 2FA or configuring OIDC/SSO federation.
-- Using Secure Compute for private networking (VPC-like).
-- Automating Vercel operations via REST API or SDK.
-- Registering webhooks for deployment events.
-- Installing and building native integrations or marketplace partners.
-- Configuring Vercel MCP for agent-driven platform automation.
-- Optimizing images via `next/image` or Vercel's Image Optimization API.
-- Generating Open Graph images with `@vercel/og`.
-- Scheduling background jobs with Vercel Cron.
-- Structuring monorepo builds and microfrontend app groups.
-- Implementing multi-tenant SaaS on Vercel.
-
-## Domain Areas
-
-### Project Configuration
-- `vercel.json` schema: functions, headers, redirects, rewrites, regions.
-- Framework detection and override settings.
-
-### RBAC & Access Groups
-- Assign Owner, Member, Viewer roles per project or team.
-- Access groups for project-level permission scoping.
-
-### Identity & Security (2FA / OIDC / Secure Compute)
-- Enforce 2FA for all team members.
-- Configure OIDC federation for CI/CD token-based auth.
-- Use Secure Compute for private egress to internal services.
-
-### REST API & SDK
-- Authenticate with `VERCEL_TOKEN`; respect rate limits.
-- Use `@vercel/sdk` (TypeScript) for typed API access.
-- Common endpoints: deployments, env vars, domains, projects.
-
-### Webhooks & Checks
-- Register webhooks for `deployment.created`, `deployment.succeeded`, etc.
-- Implement deployment checks (CI gates) via the Checks API.
-
-### Integrations & Marketplace
-- Install native integrations (e.g., observability, storage).
-- Build marketplace partner integrations with OAuth and webhooks.
-
-### MCP for Agents
-- Run Vercel MCP server locally or in CI for agent workflows.
-- Use for automated deployment queries, log retrieval, and config changes.
-
-### Image Optimization & OG Images
-- Use `next/image` for automatic format conversion and resizing.
-- Generate OG images on the fly with `@vercel/og` (ImageResponse).
-- Cache OG images appropriately.
-
-### Cron Jobs
-- Define cron schedules in `vercel.json` under `crons`.
-- Secure cron handler endpoints with `CRON_SECRET`.
-- Monitor cron execution logs in Vercel dashboard.
-
-### Monorepos
-- Configure `rootDirectory` per project for monorepo packages.
-- Use Turborepo + Vercel Remote Cache for fast incremental builds.
-
-### Microfrontends
-- Define app groups and routing in Vercel Microfrontends config.
-- Route per-path segments to independent Next.js apps.
-
-### Multi-Tenant Architecture
-- Use hostname-based routing in middleware for tenant resolution.
-- Scope environment variables and storage per tenant.
-- Combine with Edge Config for real-time tenant config.
-
-## Operating Checklist
-1. Audit and lock project configuration in `vercel.json`.
-2. Review and tighten RBAC roles; remove over-privileged members.
-3. Enforce 2FA for all team members; configure OIDC for CI.
-4. Validate REST API token scopes; rotate stale tokens.
-5. Test webhook delivery with replay; implement idempotent handlers.
-6. Verify cron endpoint security with `CRON_SECRET` validation.
-7. Validate monorepo build filtering and Turborepo cache hit rates.
-
-## Output Contract
-- `vercel.json` configuration with annotated sections
-- RBAC role matrix and access group definitions
-- Identity/SSO configuration steps and validation evidence
-- REST API and SDK integration patterns
-- Webhook handler implementation with idempotency
-- Architecture diagram for monorepo/microfrontend/multi-tenant setup
-- Residual risks and follow-up actions

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-routing/SKILL.md

@@ -1,70 +0,0 @@
----
-name: vercel-routing
-description: "Vercel edge routing: middleware patterns, redirects/rewrites, Edge Config for real-time config without redeploys, Edge Config integrations, and Node.js migration paths."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, routing, middleware, redirects, rewrites, edge config, edge config integrations, edge to node, a/b routing, geo routing, edge middleware
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: nextjs-developer, vercel-functions, vercel-caching, vercel-flags
-  consolidates: vercel-routing-middleware, vercel-redirects-rewrites, vercel-edge-config, vercel-edge-config-integrations, vercel-edge-to-node-migration
----
-
-# Vercel Routing
-
-## Purpose
-Configure Vercel's edge routing layer with middleware patterns, redirect/rewrite rules, real-time Edge Config for runtime configuration, and migration paths away from the edge runtime.
-
-## When To Use
-- Writing Vercel Middleware for auth, geo-routing, A/B testing, or bot checks.
-- Configuring redirects and rewrites in `vercel.json` or Next.js config.
-- Using Edge Config for real-time feature toggling or config without redeploys.
-- Integrating Edge Config with third-party providers (LaunchDarkly, etc.).
-- Migrating edge-incompatible middleware to Node.js functions.
-
-## Domain Areas
-
-### Middleware
-- Author `middleware.ts` with `NextRequest`/`NextResponse` or Web APIs.
-- Apply auth checks, geo-redirects, A/B bucket assignment.
-- Use `matcher` config to scope execution precisely.
-- Mind cold start and bundle size constraints (1MB limit).
-
-### Redirects & Rewrites
-- Configure in `vercel.json` under `redirects` / `rewrites`.
-- Permanent (308) vs temporary (307) redirects.
-- Capture groups and dynamic path rewriting.
-- Header-based and query-based conditional rewrites.
-
-### Edge Config
-- Create and populate Edge Config stores via dashboard or CLI.
-- Read in middleware with `@vercel/edge-config` SDK.
-- Zero-redeploy config changes for feature flags and kill switches.
-
-### Edge Config Integrations
-- Connect Edge Config to third-party providers.
-- Sync external flag state into Edge Config automatically.
-
-### Edge-to-Node Migration
-- Identify middleware using Node.js-incompatible APIs.
-- Refactor to Node.js serverless functions or API routes.
-- Use `runtime: 'nodejs'` config override.
-
-## Operating Checklist
-1. Audit middleware bundle size and strip unnecessary dependencies.
-2. Validate matcher patterns cover only intended routes.
-3. Test redirect rules for cyclic redirect risk.
-4. Populate Edge Config with safe defaults before enabling reads.
-5. Document Edge Config keys and owners; restrict write access.
-6. Plan edge-to-node migration with regression test coverage.
-
-## Output Contract
-- Middleware implementation with matcher config
-- Redirect/rewrite rule set with conflict analysis
-- Edge Config schema, population scripts, and read integration
-- Edge-to-node migration plan with test strategy
-- Performance impact assessment (middleware execution time)

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vercel-storage/SKILL.md

@@ -1,66 +0,0 @@
----
-name: vercel-storage
-description: "Vercel Storage solutions: Blob for file storage, Marketplace Postgres, Marketplace Redis, and storage migration strategies between providers."
-license: MIT
-metadata:
-  author: cubis-foundry
-  version: "1.0.0"
-  domain: vercel
-  triggers: vercel, storage, blob, postgres, redis, kv, storage migration, file upload, vercel blob, vercel postgres, vercel redis
-  role: specialist
-  scope: implementation
-  output-format: checklist
-  related-skills: database-design, database-optimizer, vercel-functions, vercel-deployments
-  consolidates: vercel-blob, vercel-marketplace-storage-postgres, vercel-marketplace-storage-redis, vercel-storage-migrations
----
-
-# Vercel Storage
-
-## Purpose
-Implement and manage Vercel Storage solutions including Blob for file/object storage, Marketplace Postgres for relational data, Marketplace Redis for caching/session state, and strategies for migrating between storage providers.
-
-## When To Use
-- Storing user-uploaded files, assets, or binary objects with Vercel Blob.
-- Provisioning a managed Postgres database via Vercel Marketplace.
-- Using managed Redis for session storage, caching, or pub/sub.
-- Migrating existing storage workloads onto or off Vercel-managed storage.
-
-## Domain Areas
-
-### Vercel Blob
-- Upload, list, and delete blobs with `@vercel/blob` SDK.
-- Client-side uploads using multipart upload tokens.
-- Set Content-Type, cache-control, and access control.
-- Integrate blob URLs with CDN delivery.
-
-### Marketplace Postgres
-- Provision and connect via `POSTGRES_URL` environment variable.
-- Use with Prisma, Drizzle, or `pg`/`postgres` client.
-- Connection pooling with Vercel Postgres connection pool.
-- Schema migrations and backup strategy.
-
-### Marketplace Redis
-- Connect via `KV_URL` / `REDIS_URL` environment variable.
-- Use `@vercel/kv` SDK or `ioredis` for session state, queues, and rate limiting.
-- Understand persistence and eviction policy defaults.
-- Multi-region replication considerations.
-
-### Storage Migrations
-- Audit current storage usage volume and access patterns.
-- Plan zero-downtime migration with dual-write phase.
-- Validate data integrity post-migration before cutover.
-
-## Operating Checklist
-1. Choose storage type based on access pattern (object vs relational vs KV).
-2. Inject connection strings via environment variables (never hard-code).
-3. Set appropriate TTL/eviction policies for Redis.
-4. Validate connection pooling config for Postgres under load.
-5. Run migration dry-run and verify checksums before full cutover.
-6. Enable auto-backup or export schedule for production data.
-
-## Output Contract
-- Storage selection rationale and architecture
-- SDK integration code and environment variable setup
-- Connection pooling and scaling configuration
-- Migration plan with dry-run and rollback steps
-- Residual risks and data integrity validation evidence

package/Ai Agent Workflow/workflows/agent-environment-setup/platforms/copilot/skills/vulnerability-scanner/SKILL.md

@@ -1,276 +0,0 @@
----
-name: vulnerability-scanner
-description: Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
-allowed-tools: Read, Glob, Grep, Bash
----
-
-# Vulnerability Scanner
-
-> Think like an attacker, defend like an expert. 2025 threat landscape awareness.
-
-## 🔧 Runtime Scripts
-
-**Execute for automated validation:**
-
-| Script | Purpose | Usage |
-|--------|---------|-------|
-| `scripts/security_scan.py` | Validate security principles applied | `python scripts/security_scan.py <project_path>` |
-
-## 📋 Reference Files
-
-| File | Purpose |
-|------|---------|
-| [checklists.md](checklists.md) | OWASP Top 10, Auth, API, Data protection checklists |
-
----
-
-## 1. Security Expert Mindset
-
-### Core Principles
-
-| Principle | Application |
-|-----------|-------------|
-| **Assume Breach** | Design as if attacker already inside |
-| **Zero Trust** | Never trust, always verify |
-| **Defense in Depth** | Multiple layers, no single point |
-| **Least Privilege** | Minimum required access only |
-| **Fail Secure** | On error, deny access |
-
-### Threat Modeling Questions
-
-Before scanning, ask:
-1. What are we protecting? (Assets)
-2. Who would attack? (Threat actors)
-3. How would they attack? (Attack vectors)
-4. What's the impact? (Business risk)
-
----
-
-## 2. OWASP Top 10:2025
-
-### Risk Categories
-
-| Rank | Category | Think About |
-|------|----------|-------------|
-| **A01** | Broken Access Control | Who can access what? IDOR, SSRF |
-| **A02** | Security Misconfiguration | Defaults, headers, exposed services |
-| **A03** | Software Supply Chain 🆕 | Dependencies, CI/CD, build integrity |
-| **A04** | Cryptographic Failures | Weak crypto, exposed secrets |
-| **A05** | Injection | User input → system commands |
-| **A06** | Insecure Design | Flawed architecture |
-| **A07** | Authentication Failures | Session, credential management |
-| **A08** | Integrity Failures | Unsigned updates, tampered data |
-| **A09** | Logging & Alerting | Blind spots, no monitoring |
-| **A10** | Exceptional Conditions 🆕 | Error handling, fail-open states |
-
-### 2025 Key Changes
-
-```
-2021 → 2025 Shifts:
-├── SSRF merged into A01 (Access Control)
-├── A02 elevated (Cloud/Container configs)
-├── A03 NEW: Supply Chain (major focus)
-├── A10 NEW: Exceptional Conditions
-└── Focus shift: Root causes > Symptoms
-```
-
----
-
-## 3. Supply Chain Security (A03)
-
-### Attack Surface
-
-| Vector | Risk | Question to Ask |
-|--------|------|-----------------|
-| **Dependencies** | Malicious packages | Do we audit new deps? |
-| **Lock files** | Integrity attacks | Are they committed? |
-| **Build pipeline** | CI/CD compromise | Who can modify? |
-| **Registry** | Typosquatting | Verified sources? |
-
-### Defense Principles
-
-- Verify package integrity (checksums)
-- Pin versions, audit updates
-- Use private registries for critical deps
-- Sign and verify artifacts
-
----
-
-## 4. Attack Surface Mapping
-
-### What to Map
-
-| Category | Elements |
-|----------|----------|
-| **Entry Points** | APIs, forms, file uploads |
-| **Data Flows** | Input → Process → Output |
-| **Trust Boundaries** | Where auth/authz checked |
-| **Assets** | Secrets, PII, business data |
-
-### Prioritization Matrix
-
-```
-Risk = Likelihood × Impact
-
-High Impact + High Likelihood → CRITICAL
-High Impact + Low Likelihood  → HIGH
-Low Impact + High Likelihood  → MEDIUM
-Low Impact + Low Likelihood   → LOW
-```
-
----
-
-## 5. Risk Prioritization
-
-### CVSS + Context
-
-| Factor | Weight | Question |
-|--------|--------|----------|
-| **CVSS Score** | Base severity | How severe is the vuln? |
-| **EPSS Score** | Exploit likelihood | Is it being exploited? |
-| **Asset Value** | Business context | What's at risk? |
-| **Exposure** | Attack surface | Internet-facing? |
-
-### Prioritization Decision Tree
-
-```
-Is it actively exploited (EPSS >0.5)?
-├── YES → CRITICAL: Immediate action
-└── NO → Check CVSS
-         ├── CVSS ≥9.0 → HIGH
-         ├── CVSS 7.0-8.9 → Consider asset value
-         └── CVSS <7.0 → Schedule for later
-```
-
----
-
-## 6. Exceptional Conditions (A10 - New)
-
-### Fail-Open vs Fail-Closed
-
-| Scenario | Fail-Open (BAD) | Fail-Closed (GOOD) |
-|----------|-----------------|---------------------|
-| Auth error | Allow access | Deny access |
-| Parsing fails | Accept input | Reject input |
-| Timeout | Retry forever | Limit + abort |
-
-### What to Check
-
-- Exception handlers that catch-all and ignore
-- Missing error handling on security operations
-- Race conditions in auth/authz
-- Resource exhaustion scenarios
-
----
-
-## 7. Scanning Methodology
-
-### Phase-Based Approach
-
-```
-1. RECONNAISSANCE
-   └── Understand the target
-       ├── Technology stack
-       ├── Entry points
-       └── Data flows
-
-2. DISCOVERY
-   └── Identify potential issues
-       ├── Configuration review
-       ├── Dependency analysis
-       └── Code pattern search
-
-3. ANALYSIS
-   └── Validate and prioritize
-       ├── False positive elimination
-       ├── Risk scoring
-       └── Attack chain mapping
-
-4. REPORTING
-   └── Actionable findings
-       ├── Clear reproduction steps
-       ├── Business impact
-       └── Remediation guidance
-```
-
----
-
-## 8. Code Pattern Analysis
-
-### High-Risk Patterns
-
-| Pattern | Risk | Look For |
-|---------|------|----------|
-| **String concat in queries** | Injection | `"SELECT * FROM " + user_input` |
-| **Dynamic code execution** | RCE | `eval()`, `exec()`, `Function()` |
-| **Unsafe deserialization** | RCE | `pickle.loads()`, `unserialize()` |
-| **Path manipulation** | Traversal | User input in file paths |
-| **Disabled security** | Various | `verify=False`, `--insecure` |
-
-### Secret Patterns
-
-| Type | Indicators |
-|------|-----------|
-| API Keys | `api_key`, `apikey`, high entropy |
-| Tokens | `token`, `bearer`, `jwt` |
-| Credentials | `password`, `secret`, `key` |
-| Cloud | `AWS_`, `AZURE_`, `GCP_` prefixes |
-
----
-
-## 9. Cloud Security Considerations
-
-### Shared Responsibility
-
-| Layer | You Own | Provider Owns |
-|-------|---------|---------------|
-| Data | ✅ | ❌ |
-| Application | ✅ | ❌ |
-| OS/Runtime | Depends | Depends |
-| Infrastructure | ❌ | ✅ |
-
-### Cloud-Specific Checks
-
-- IAM: Least privilege applied?
-- Storage: Public buckets?
-- Network: Security groups tightened?
-- Secrets: Using secrets manager?
-
----
-
-## 10. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Scan without understanding | Map attack surface first |
-| Alert on every CVE | Prioritize by exploitability + asset |
-| Ignore false positives | Maintain verified baseline |
-| Fix symptoms only | Address root causes |
-| Scan once before deploy | Continuous scanning |
-| Trust third-party deps blindly | Verify integrity, audit code |
-
----
-
-## 11. Reporting Principles
-
-### Finding Structure
-
-Each finding should answer:
-1. **What?** - Clear vulnerability description
-2. **Where?** - Exact location (file, line, endpoint)
-3. **Why?** - Root cause explanation
-4. **Impact?** - Business consequence
-5. **How to fix?** - Specific remediation
-
-### Severity Classification
-
-| Severity | Criteria |
-|----------|----------|
-| **Critical** | RCE, auth bypass, mass data exposure |
-| **High** | Data exposure, privilege escalation |
-| **Medium** | Limited scope, requires conditions |
-| **Low** | Informational, best practice |
-
----
-
-> **Remember:** Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: "What would an attacker do with this?"