Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add roedyrustam/vibes-plug --skill self-healing-cloud-orchestratorgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/roedyrustam/vibes-plug/self-healing-cloud-orchestrator)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/self-healing-cloud-orchestrator"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/self-healing-cloud-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/self-healing-cloud-orchestrator"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/self-healing-cloud-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00053 | $0.02334 |
| Opus 5.5 | $0.00021 | $0.00934 |
| Sonnet 5.5 | $0.00011 | $0.00467 |
| Haiku 4.5 | $0.00005 | $0.00233 |
Grade A, and why
self-healing-cloud-orchestrator scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
import { execSync } from 'node:child_process'; How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-Healing Cloud Orchestrator (Code-to-Cloud Auto Remediation)
English
Orchestration & Integration
- Upstream & Polling Sentinel:
proactive-background-watcher(background poll loop & cron checks),zero-to-prod-orchestrator(Phase 8 operations). - Telemetry & Error Ingestion:
logging-error-tracking-expert(structured JSON logs from Pino/Winston/Sentry),data-telemetry-expert(OpenTelemetry metrics & trace correlation). - Local TDD Patching & Verification:
autonomous-tdd-debugger(iterative local unit/regression validation),property-mutation-testing-expert(preventing patch regressions). - CI/CD & Cloud Deployment:
ci-cd-devops-architect(git branch creation, PRs, deployment pipelines),cloud-hosting-expert(Vercel/Railway rollback & redeploy).
Description
Bridges the gap between code generation and Cloud Operations (CloudOps). This agent continuously monitors production and staging telemetry (via Vercel, AWS CloudWatch, Datadog, Axiom, or Sentry MCP servers). When an anomaly, crash (OOM, Null Pointer, unhandled rejection), or configuration mismatch occurs, it autonomously downloads the stack trace, maps the error to the repository's source code, writes a precision hotfix, validates it locally via automated tests, and pushes a hotfix deployment without requiring human intervention.
Trigger Conditions
- Post-deployment in Phase 8, running as a persistent background daemon or webhook receiver.
- Spike in 5xx HTTP response codes or uncaught exception rate > 1%.
- Critical health-check failure detected by
proactive-background-watcher. - Memory leak or container crash-loop backoff reported by container orchestrator.
Core Operating Protocol
Telemetry Alert (Sentry / Datadog)
│
▼
1. Triage & Deduplication ──► Extract Stack Trace & Commit SHA
│
▼
2. AST Symbol Mapping ─────► Locate Exact Source File & Line
│
▼
3. Autonomous Patching ────► Apply Null-Safe / Error Boundary Fix
│
▼
4. Test Verification ──────► Run Vitest / Playwright (autonomous-tdd-debugger)
│
├─► PASS ──► Push `hotfix/auto-*` branch & trigger CI/CD deploy
└─► FAIL ──► Retry (Max 3 attempts) or Trigger Canary Rollback
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago Changed 7799fd30397f
- 7d ago Changed · +1 lines cc9b5208abdc
- 10d ago Changed · +135 lines 04b6e0e785bf
- 19d ago Changed bdc09283e4dc
- 24d ago Changed 6d2ddd02b845
- 25d ago Changed 152d9a0bfd15
- 27d ago Changed · -6 lines · +37 tokens per session e22b979d1886
- 29d ago Changed · +6 lines · -37 tokens per session 999789242e85
- 1mo ago Changed a15f1209883e
- 1mo ago First seen · 58 lines · 53 tokens per session scan A 2d5a57173bfa
self-healing-cloud-orchestrator is a skill published in the GitHub repository roedyrustam/vibes-plug (115 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 2,334 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
gke-workload-troubleshooting
Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.
application-integration-troubleshooting
Diagnoses failed, stuck, or silent Google Cloud Application Integration runs and Integration Connectors tasks using the REST API, Cloud Logging, and Cloud Monitoring. Use when an integration fails, returns HTTP 200 without doing the expected work, hangs in a suspended or retry state, or hits IAM, run-as service…
gke-ai-troubleshooting-tpu-mxla-hang
Diagnose GKE Cloud TPU multi-slice training hangs (Megascale HANGDETECTED logs and hang monitored events) using the ML Diagnostics Megascale XLA (MXLA) Hang Analyzer (gcloud alpha mldiagnostics monitored-events) and 1-minute Cloud Monitoring multi-slice latency metrics (kubernetes.io/container/multislice/).…
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…