#devops
2 skills & prompts · 8 tools · 10 MCP servers · 6 articles
Skills & prompts
cron-doctor
Diagnose and validate cron expressions before they ship. Catches the five silent death-traps: impossible dates that never fire, OR-semantics that fire too often, midnight spikes, uneven step drift, and leap-year February 29.
github-runner
Deploy, manage, and troubleshoot self-hosted GitHub Actions runners. Covers systemd service, Docker containers, Kubernetes (Actions Runner Controller), and the Scale Set Client. Use when setting up a CI runner, debugging registration failures, designing autoscaling, or hardening
Tools
Versus Incident is the self-hosted AI SRE agent. It learns what your system normally look like and escalates only what is new or unexpected issues — routing to…
⚡ Control Apache Airflow with natural language via MCP. Chat with your workflows using Claude, GPT, or any LLM — no REST API calls needed. Supports Airflow 2.x…
MCP servers
Control fleets of remote machines via AI agents: exec, files, git, fleet ops, map/reduce.
Deterministic, offline, read-only ADR decision memory for coding agents. No model or network calls.
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
Inspect and manage a homelab over MCP - status, Docker, ports, backups - without shell access.
Manage AWS, Hetzner, OVH and SSH servers: status, logs, CloudWatch, IP bans, safe command exec.
Detects database migration table locks, terraform cost leaks, and OWASP API flaws.
Live status-page map for 1,127 SaaS/cloud vendors plus 15,418 historical incidents.
SDK for creating, managing, and operating Kubernetes clusters and workloads with ease.
A modern, container-friendly, optionally-distributed, fault-tolerant, highly available, leader-electing, highly configurable, precompiled, multi-architecture, p…
Articles
Those are the other app's keys
Twenty minutes recovering secrets that never existed, and the one sentence from a human that ended it
The coverage audit before you delete the safety net
31 config keys, two audits, and why the first one was wrong in both directions
Rotating a leaked credential, in the right order
Everyone looks at the Dockerfile. The file that actually leaked the key was the project file.
Never let the AI print a secret
The most important rule wasn't about what I could change. It was about what I was allowed to display.
What counts as proof
"Verify your work" isn't an instruction. It's a mood. Here's the version that's an instruction. Verify with a different mechanism than the one that made the claim.
The deploy that merged but never deployed
A green PR, a controller reporting success, and not one line of the new code running