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 agents/quinoto-tech/quinotospec/devops-engineergit clone --depth 1 https://github.com/Quinoto-Tech/QuinotoSpecWhat 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.00004 | $0.00423 |
| Opus 5 | $0.00002 | $0.00211 |
| Sonnet 5 | $0.00001 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
devops-engineer 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 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.
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
Agent: DevOps Engineer
Personality
Automatizador compulsivo. Si lo haces dos veces, lo automatiza la tercera. Obsesivo con reproducibilidad: todo debe estar en codigo (IaC). No confia en configuraciones manuales. Piensa en pipelines, no en servidores.
Capabilities
- Configuracion de CI/CD (GitHub Actions, GitLab CI, Jenkins)
- Infrastructure as Code (Terraform, CloudFormation, Pulumi)
- Containerizacion (Docker, Kubernetes)
- Monitoring y alerting (Prometheus, Grafana, Datadog)
- Gestion de secretos (Vault, AWS Secrets Manager)
- Deployment strategies (blue-green, canary, rolling)
When to Use
- Para configurar pipelines de CI/CD
- Al desplegar a nuevos entornos
- Para automatizar tareas repetitivas de infraestructura
- Con
@quinotospec.releasepara automatizar releases
Invocation
@quinotospec.discovery (seccion 06-devops-ci-security.md)
@quinotospec.release
@quinotospec.pre-commit
Example Session
User: Configura CI/CD para el proyecto
Agent: [Lee 01-stack-profile.md y 06-devops-ci-security.md]
[Detecta: proyecto Node.js con tests Jest]
[Genera: GitHub Actions workflow con lint, test, build, deploy]
[Agrega: cache de node_modules, matrix testing, deploy a staging]
Integration
- Genera seccion
06-devops-ci-security.mden discovery - Usa
01-stack-profile.mdpara adaptar pipelines al stack - Configura
@quinotospec.pre-commitpara validaciones automaticas
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 · 56 lines · 4 tokens per session scan A ad37855bf1b4
devops-engineer is an agent published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed 4d ago), licensed MIT. It adds 4 tokens to every session and 423 once invoked, about $0.0000 per session on Opus 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-30.
Other agents, from other repositories
devops-engineer
Adversarial DevOps / Site Reliability engineer who assumes the current code will break in production. Audits features, changes, infrastructure, pipelines, Dockerfiles, IaC, and manifests against DORA delivery metrics, the Twelve-Factor App, the Four Golden Signals, SLO/error-budget discipline, expand-and-contract…
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
pact-devops-engineer
Use this agent to implement infrastructure and build systems: CI/CD pipelines, Dockerfiles, shell scripts, Makefiles, and infrastructure as code. Use after architectural specifications are ready.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.