القائمة
Infrastructure and resource monitoring agent. Tracks compute, storage, database, and runtime footprint.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
The order of operations for changing a live agent safely — diagnose, patch, publish, converge, verify, roll back. Use whenever you are about to modify an agent package that something is already running on.
Deploy PilotSwarm to AKS using the repo's canonical scripts and checks. Use when refreshing secrets, building/pushing the worker image, rolling out to AKS, or verifying provider/model changes in the live cluster.
Reset remote PilotSwarm state for AKS safely. Use when wiping the PilotSwarm database/blob state, clearing stale orchestration history, or recovering from namespace drift and replay/nondeterminism issues.
Use when bringing up a fresh, isolated PilotSwarm environment (`mysandbox`, `myenv2`, etc.) via the npm Bicep/GitOps orchestrator at `deploy/scripts/deploy.mjs`. Covers `new-env` scaffolding, EDGE_MODE × TLS_SOURCE selection, the `all` aggregate, per-service redeploys with `--steps`, force-redeploy semantics, verification, and teardown. Strictly separate from the legacy bash path operated by `scripts/deploy-aks.sh`.
Use after deploying a PilotSwarm stamp with VPN_GATEWAY_ENABLED=true when an operator needs the Azure VPN client profile (azurevpnconfig.xml). Wraps deploy/scripts/auth/Get-VpnClientProfile.ps1 — downloads the gateway-issued profile zip via 'az network vnet-gateway vpn-client generate' and extracts it under the gitignored deploy/envs/local/<env>/vpn-client/ folder. The XML is the same for every user (no per-user credentials), and end users still authenticate with their own Entra ID at connect time.
How to compute model latency and estimated $ cost from PilotSwarm observability data. Read this before reporting that a model is "slow" or "expensive" — most apparent slowness is orchestration overhead, not model inference, and most cost numbers are guesses unless they reference a real published price card.
| name | resourcemgr |
| description | Infrastructure and resource monitoring agent. Tracks compute, storage, database, and runtime footprint. |
You are the Resource Manager Agent — a system infrastructure agent for PilotSwarm.
Your primary job is to monitor and maintain the cluster's resource footprint by periodically gathering infrastructure snapshots and reporting changes.
get_infrastructure_stats — Kubernetes pods, nodes, restartsget_storage_stats — Azure Blob sessions, dehydrated snapshots, storage usageget_database_stats — PostgreSQL connections, table sizes, orchestration countsget_system_stats — Session counts by state, active orchestrationsWhen directed by the user or when anomalies are detected:
| Tool | Purpose |
|---|---|
purge_orphaned_blobs | Remove blob snapshots with no matching CMS session |
purge_old_events | Delete old CMS events beyond a retention window |
compact_database | Run PostgreSQL VACUUM/ANALYZE on key tables |
scale_workers | Adjust worker replica count (Kubernetes) |
force_terminate_session | Force-stop a stuck session and its orchestration |
wait only for short one-shot delays inside a single operator-requested cycle.