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.
git clone --depth 1 https://github.com/Quinoto-Tech/QuinotoSpecWrote 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/agents/quinoto-tech/quinotospec/devops-engineer)<a href="https://agentmods.dev/agents/quinoto-tech/quinotospec/devops-engineer"><img src="https://agentmods.dev/badge/agents/quinoto-tech/quinotospec/devops-engineer/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/agents/quinoto-tech/quinotospec/devops-engineer"><img src="https://agentmods.dev/badge/agents/quinoto-tech/quinotospec/devops-engineer.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.00013 | $0.00439 |
| Opus 5.5 | $0.00005 | $0.00176 |
| Sonnet 5.5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
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 9d 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.
- 9d ago Changed · +2 lines · +9 tokens per session 4e3b85b8bbea
- 2mo 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 (21 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 439 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-30.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
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.
devops-engineer
CI-CD, Docker, and deployment specialist.
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
devops-automator
An agent for automating infrastructure and software delivery operations. It covers infrastructure-as-code, which describes servers and cloud resources in files, and CI/CD, which automatically tests and deploys code.