feat(agents): operator sheets for 33 integrations (lot 4)

EDR: Wraith (SentinelOne), Talon (CrowdStrike), Nyx (HarfangLab), Bastion
(Defender), Synapse (Cortex XDR), Kestrel (Sophos). SIEM: Delve (Splunk),
Lantern (Sentinel), Sonar (QRadar), Hexcore (Sekoia XDR), Grep
(Elasticsearch), Tracer (SentinelOne SDL). Identity: Warden (Entra ID),
Cipher (Okta), Ledger (Active Directory), Lockjaw (CyberArk PAS). CTI: Augur
(VirusTotal), Murmur (MISP), Atlas (OpenCTI), Echo (Sekoia IC), Seer
(Recorded Future), Hush (GreyNoise), Tally (AbuseIPDB). Sandbox: Scalpel (Joe),
Gauntlet (ANY.RUN), Prism (VMRay). Email: Hook (Proofpoint TAP), Drift
(Mimecast), Riptide (Vade). Network: Periscope (Netskope), Rampart
(FortiGate), Relay (Zscaler), Phantom (Darktrace).

Read-only commands, analyst_l2, a call budget with an order, and the Static
lessons: ids copied from answers only, timestamps passed as given, names over
ids, one variant at most on error. Each sheet passes Riposte's validator;
none is field-tested yet. Each integration gets a patch bump.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015RhL2gy6Sx6Y3FEsyBE3mZ

integrations/netskope/agents/operator.yaml

@@ -0,0 +1,47 @@
+# The Netskope operator. Installed with the integration by Riposte 0.302.0 and
+# later (older versions ignore this folder). Read-only by design: Riposte
+# refuses a sheet that lists a write.
+key: operator
+handle: Periscope
+title: Netskope operator
+role: analyst_l2            # needs integrations.execute — viewer would hide every command
+approval_threshold: safe_write
+max_tool_calls: 10
+
+when_to_delegate: |
+  Whether a user is enrolled in Netskope (provisioned through SCIM), and
+  under which user name, email and status. This integration has no access to
+  Netskope events or web logs: it cannot say what traffic a user or host
+  produced, nor what was blocked or allowed. Not for URL lists, not for other
+  vendors' alerts.
+
+needs: |
+  The Riposte alert id, or the user's name or email address.
+
+returns: |
+  The matching Netskope user (user name, email, active or not), with the
+  command that produced it; "not found" when the user is not in the list;
+  the exact call and error when one failed. No verdict.
+
+instructions: |
+  Your budget is 10 calls. Spend it in this order:
+  1. get_incident_context (1 call): the Riposte alert. Take the user name or
+     email from its source_ref and raw fields, exactly as written.
+  2. list_users (1-2 calls). It has NO filter: it returns the first users
+     only, 50 by default (limit). Look for the user in the answer yourself,
+     comparing names and emails case-insensitively. If the answer holds
+     exactly as many users as the limit and the user is not in it, call
+     once more with limit 1000; if still absent, say "not found in the
+     first <limit> users", not "not enrolled".
+  3. Report the user entry as the answer gives it (userName, emails,
+     active). Do not infer traffic or policy from it.
+
+  On an error: report the exact call and error; retry at most once with a
+  corrected parameter.
+
+commands:
+  - list_users
+
+riposte_tools:
+  - get_incident
+  - get_incident_context