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 m3taz-ahmed/ai-globals --skill devops-lordgit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/devops-lord)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/devops-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/devops-lord/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/m3taz-ahmed/ai-globals/devops-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/devops-lord.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00036 | $0.00773 |
| Opus 5.5 | $0.00014 | $0.00309 |
| Sonnet 5.5 | $0.00007 | $0.00155 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
devops-lord scanned grade A with 0 findings 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 1mo 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
[SKILL] devops-lord [OBJ] Design, build, and operate delivery pipelines and runtime platforms. [RULES]
- [CMD] IDs: Docker
/docker/docs, Kubernetes/kubernetes/website, Podman/websites/podman_io_en, Helm/helm/helm-www, Terraform/websites/developer_hashicorp_terraform, Pulumi/pulumi/docs, Ansible/websites/ansible_projects_ansible. - [REQ] Pillar coverage: images/layers/registries, runtimes (Docker/Podman rootless), orchestration, packaging (Helm/OCI), IaC (Terraform/Pulumi), config-mgmt (Ansible), CI/CD/GitOps, observability/reliability, security/cost.
- [REQ] Query relevant ID with full question + topic (Dockerfile, kubernetes, helm, terraform, ansible).
- [REQ] Compare tools by concrete differences: daemon vs rootless, state backend, language support.
- [REQ] Prefer current docs; container/K8s APIs change fast.
- [REQ] Images: multi-stage builds, minimal/distroless bases, non-root USER, .dockerignore, pinned digests, SBOM + Cosign sign, scan in CI (Trivy/Grype). Never ship
:latestto prod. - [REQ] Kubernetes production baseline: resource requests AND limits (requests=reservation, limits=safety net), liveness ≠ readiness probes (crash-loop risk if conflated), PodDisruptionBudgets, NetworkPolicy default-deny, namespaces as tenancy boundaries, Helm/Kustomize for packaging — no raw kubectl-apply snowflakes.
- [REQ] Workload placement: Deployments for stateless, StatefulSets for identity/storage-bound, DaemonSets for node agents, Jobs/CronJobs for batch. HPA on real metrics (CPU only as fallback); VPA recommendations reviewed not auto-applied.
- [REQ] IaC doctrine: state remote + locked + versioned; modules for repeated patterns with versioned releases;
planoutput is the PR description; drift detection scheduled; secrets NEVER in state-visible values (use data sources/refs). - [REQ] GitOps: cluster desired state in git (ArgoCD/Flux), app-of-apps for multi-env, image updaters or CI-driven manifest PRs, sync waves + health gates for ordering, drift = alert not manual fix.
- [REQ] Config management (Ansible): idempotent plays (check mode clean), roles for reuse, vault for secrets, immutable infra preferred over long-lived managed hosts where possible.
- [REQ] Pipeline supply chain: OIDC keyless cloud auth, pinned action SHAs, artifact provenance (SLSA), deploy only scanned+signed artifacts, environment protection rules + approvals for prod.
- [REQ] Observability stack: Prometheus + Grafana (or cloud-native), Loki/ELK for logs, OTel traces; alerts on symptoms/SLOs; every service ships with health endpoints + dashboards.
- [REQ] Cost: requests right-sized from actual usage (not guesses), spot/preemptible for interruptible work, autoscaling both directions, cluster/storage sprawl cleaned on schedule.
- [PROHIBIT] Privileged containers without justification, hostPath mounts on multi-tenant clusters,
apply -fagainst prod without review, secrets in ConfigMaps/env literals, or IaC applied outside the pipeline.
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.
- 1mo ago Changed · +10 lines 834528afc14d
- 1mo ago First seen · 13 lines · 36 tokens per session scan A 4074559ae56a
devops-lord is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed 5d ago), licensed MIT. It adds 36 tokens to every session and 773 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
devops-automator
Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation. Activate on: CI/CD, GitHub Actions, Terraform, Docker, Kubernetes, Helm, ArgoCD, GitOps, deployment pipeline, infrastructure as code, container orchestration. NOT for: application code (use language skills), database schema (use…
CI/CD Pipeline Advanced
Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.
test-environments
Design environment strategy for testing across dev, CI, preview, staging, and production — Docker Compose test infrastructure, multi-stage Dockerfiles, seed-data lifecycle, per-PR preview environments, production parity, and external-dependency stubbing at the HTTP boundary. Use when: "set up test environment,"…