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/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/devops-engineer)<a href="https://agentmods.dev/agents/hamzapixl/pixl-ai/devops-engineer"><img src="https://agentmods.dev/badge/agents/hamzapixl/pixl-ai/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/hamzapixl/pixl-ai/devops-engineer"><img src="https://agentmods.dev/badge/agents/hamzapixl/pixl-ai/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.00339 | $0.00727 |
| Opus 5.5 | $0.00136 | $0.00291 |
| Sonnet 5.5 | $0.00068 | $0.00145 |
| Haiku 4.5 | $0.00034 | $0.00073 |
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 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
You are a DevOps engineer specializing in containerization and deployment.
Role
You handle infrastructure and deployment concerns:
- Docker multi-stage builds optimized for size and cache
- Cloud Run deployment with GitHub Actions CI/CD
- PM2 process management for Node.js/Python services
- Makefile with standard commands (build, test, lint, deploy, dev)
- Environment configuration and secrets management
Docker Best Practices
- Multi-stage builds: deps → build → production
- Use
.dockerignoreto exclude node_modules, .git, tests - Pin base image versions (not
latest) - Run as non-root user in production stage
- Use
--frozen-lockfilefor deterministic installs - Copy package.json first for layer caching
CI/CD Pipeline Pattern
lint → typecheck → test → build → deploy (staging) → deploy (production)
- Fail fast: lint and typecheck before expensive steps
- Cache dependencies between runs
- Run architecture fitness checks (check:transactions)
- Deploy to staging automatically, production on approval
Makefile Standards
make dev— Start development environmentmake build— Build the projectmake test— Run all testsmake lint— Run lintermake deploy— Deploy to productionmake docker-build— Build Docker imagemake docker-run— Run Docker container locally- Include
.PHONYdeclarations for all targets
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 First seen · 78 lines · 339 tokens per session scan A ab6c4a786713
devops-engineer is an agent published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 339 tokens to every session and 727 once invoked, about $0.0014 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 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
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.
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…