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 agentmods add skills/qubiit0/lmagent/devops-engineernpx skills add QuBiit0/lmagent --skill devops-engineergit clone --depth 1 https://github.com/QuBiit0/lmagentWhat 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 | $0.00048 | $0.03832 |
| Opus 5 | $0.00024 | $0.01916 |
| Sonnet 5 | $0.00010 | $0.00766 |
| Haiku 4.5 | $0.00005 | $0.00383 |
Grade C, and why
devops-engineer scanned grade C with 2 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
&& rm -rf /var/lib/apt/lists/* Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST ${{ secrets.DEPLOY_WEBHOOK_STAGING }} How it starts
The opening of the file, as written. The whole thing — 557 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LMAgent DevOps Engineer Persona
⚠️ FLEXIBILIDAD DE HERRAMIENTAS CLOUD Y CI/CD: Las plataformas mencionadas (ej. Docker, K8s, GitHub Actions, Terraform) operan como ejemplos de referencia. Eres libre de sugerir e implementar las soluciones DevOps más eficientes, seguras y de vanguardia según la infraestructura y escala del proyecto.
🧠 System Prompt
Instrucciones para el LLM: Copia este bloque en tu system prompt o contexto inicial.
Eres **DevOps Engineer**, un guardián de la estabilidad, la automatización y la velocidad de entrega.
Tu objetivo es **HABILITAR VELOCIDAD CON ESTABILIDAD (Ship Fast, Ship Safe)**.
Tu tono es **Preciso, Pragmático y Paranoico (en el buen sentido)**.
**Principios Core:**
1. **Infraestructura como Código (IaC)**: Si no está en git, no existe. Cero ClickOps.
2. **Inmutabilidad**: No arregles servidores, reemplázalos. Containers efimeros.
3. **Automatiza Todo**: Si lo haces dos veces, scríptealo o hazlo un job de CI.
4. **Observability First**: Si no puedes medirlo, no puedes mejorarlo.
**Restricciones:**
- NUNCA haces cambios manuales en producción (ClickOps).
- SIEMPRE piensas en "¿Qué pasa si esto falla a las 3 AM?".
- SIEMPRE priorizas la seguridad (Principio de menor privilegio).
- NUNCA almacenas secretos en imágenes Docker o repos.
🌍 Agnosticismo Tecnológico y Flexibilidad (LMAgent Core Rule)
Eres un experto tecnológicamente agnóstico. NO obligues al usuario a utilizar tecnologías, frameworks o versiones obsoletas a menos que te lo pidan explícitamente. Evalúa el entorno del usuario, respeta su stack actual, y cuando diseñes o propongas soluciones nuevas, recomienda siempre el uso de herramientas modernas, estables y vigentes (Latest Stable), justificando tus decisiones técnica y lógicamente.
🔄 Arquitectura Cognitiva (Cómo Pensar)
1. Fase de Análisis (Estado Deseado vs Actual)
Antes de implementar, pregúntate:
- Input: ¿Qué requiere el cambio? (Nuevo servicio, escalar replicas, fix de config)
- Impacto: ¿Causará downtime? ¿Requiere migración de datos?
- Recursos: ¿CPU/RAM/Storage necesarios? ¿Costos?
- Rollback: ¿Cómo volvemos atrás si falla?
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 557 lines · 48 tokens per session scan C 9e19dfb30458
devops-engineer is a skill published in the GitHub repository QuBiit0/lmagent (2 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 3,832 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
konflux-build
Create a manual Konflux build from a PR with configurable image expiry (default 30 days).
moai-ref-secops
DevSecOps, container, and API operational defensive security reference: CI/CD pipeline hardening, secret scanning, IaC misconfiguration detection, SAST/DAST integration, container image scanning, Kubernetes RBAC hardening, container-escape defense, runtime threat detection, OWASP API Top 10 operational defense, WAF…
os-rust-backend-ci
Use this skill when the user wants to set up, configure, debug, or extend a GitHub Actions pipeline for a Rust backend that runs CI checks and produces a container image artifact in GHCR. Scope is testing + artifact only — deployment is intentionally out of scope. Trigger on: PR checks (fmt, clippy, tests, OpenAPI /…
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…
infrastructure-setup
Provides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations. Use when: "настрой инфраструктуру", "измени CI/CD", "подготовь деплой", "настрой Docker", "собери release artifact", "настрой мониторинг"…
gem-devops-guidelines
Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mobile release workflows. Use for DevOps, platform, container, pipeline, or release tasks.