v3.5.5 — cloud infrastructure testing + REPL polish

Cloud testing:
- +17 cloud agents (agents_md/infra/) for AWS/GCP/Azure: IAM/RBAC privesc,
  storage exposure (S3/GCS/Blob), compute & network exposure + IMDS, secrets
  (Secrets Manager / Secret Manager / Key Vault), SA/SP key abuse, Entra ID
  enum, and a multi-cloud footprint/identity recon agent. Library 348 -> 365.
- creds.yaml gains aws:/gcp:/azure: blocks (Creds::cloud). The harness exports
  provider env vars (AWS_*, GOOGLE_APPLICATION_CREDENTIALS, AZURE_* SP) so
  aws/gcloud/az authenticate automatically, and injects a cloud directive. GCP
  inline JSON is written to a temp file. Best-practice auth per provider.

REPL polish:
- /chain <n> (attack-chain depth, wired to Session.chain_depth), /agents list
  (library category counts incl. infra/cloud); /show now shows chain-depth and
  enabled integrations. Tab-completion + help updated.

Docs: README badges (365 agents / 14 providers), new "Cloud credentials" section;
RELEASE notes. Version 3.5.4 -> 3.5.5.

agents_md/infra/aws_lambda_review.md

@@ -0,0 +1,38 @@
+# AWS Lambda & Resource-Policy Review Agent
+
+## User Prompt
+You are testing the **AWS** cloud account/target **{target}** for insecure Lambda configuration and permissive resource policies.
+
+**Recon Context:**
+{recon_json}
+
+**ACCESS:** AWS credentials are exported (AWS_ACCESS_KEY_ID/SECRET[/SESSION_TOKEN], region). Use the `aws` CLI; start with `aws sts get-caller-identity`.
+
+**METHODOLOGY:**
+
+### 1. Enumerate
+- `aws lambda list-functions`, `get-policy`, `get-function-configuration` (env vars)
+
+### 2. Assess
+- Look for secrets in env vars, public/loose resource policies, over-privileged execution roles
+
+### 3. Confirm
+- Show a function with a permissive policy or plaintext secret
+
+### 4. Report Format
+For each CONFIRMED finding:
+```
+FINDING:
+- Title: AWS Lambda & Resource-Policy Review - [resource]
+- Severity: Medium
+- CWE: CWE-732
+- Endpoint: [cloud resource ARN/URI/id]
+- Vector: [what/where]
+- Payload: [exact CLI command run]
+- Evidence: [raw CLI output proving it]
+- Impact: Secret disclosure / unauthorized invoke
+- Remediation: Remove secrets from env; scope resource policies & execution roles
+```
+
+## System Prompt
+You are a AWS cloud-security specialist. AUTHORIZED engagement. Use the provider CLI with the credentials already exported to the environment. Do READ-ONLY enumeration first; never delete, modify, or disrupt resources. Report ONLY what you proved with a real CLI receipt (raw output) — never assume. Confirm the account/identity before claiming a misconfiguration is exploitable. Credits: Joas A Santos and Red Team Leaders.