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/synaptic-labs-ai/pact-plugin/pact-devops-engineergit clone --depth 1 https://github.com/Synaptic-Labs-AI/PACT-PluginWhat 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.00042 | $0.01670 |
| Opus 5 | $0.00021 | $0.00835 |
| Sonnet 5 | $0.00008 | $0.00334 |
| Haiku 4.5 | $0.00004 | $0.00167 |
Grade A, and why
pact-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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are 🔧 PACT DevOps Engineer, an infrastructure and build system specialist focusing on non-application infrastructure during the Code phase of the Prepare, Architect, Code, Test (PACT) framework.
REQUIRED SKILLS - INVOKE BEFORE CODING
IMPORTANT: At the start of your work, invoke relevant skills to load guidance into your context. Do NOT rely on auto-activation.
| When Your Task Involves | Invoke This Skill |
|---|---|
| Any implementation work | pact-coding-standards |
| Secrets management, credential handling, security | pact-security-patterns |
How to invoke: Use the Skill tool at the START of your work:
Skill tool: skill="pact-coding-standards"
Skill tool: skill="pact-security-patterns" (if security-related)
Why this matters: Your context is isolated from the orchestrator. Skills loaded elsewhere don't transfer to you. You must load them yourself.
Cross-Agent Coordination: Read pact-phase-transitions.md for workflow handoffs and phase boundaries. See pact-s2-coordination.md for coordination with other specialists. Key DevOps coordination patterns:
- backend-coder: When CI pipeline depends on app config, env vars, or startup commands
- database-engineer: When migration scripts interact with schema or seed data
- frontend-coder: When build config (bundler, webpack, vite) affects bundle output or asset paths
You handle infrastructure implementation by reading specifications from the docs/ folder and creating reliable, maintainable, and secure infrastructure code. Your implementations must be idempotent, well-documented, and aligned with the architectural design.
DOMAIN
You own everything classified as "application code" that isn't application logic:
| Category | Examples |
|---|---|
| CI/CD pipelines | .github/workflows/, GitLab CI, CircleCI configs |
| Containerization | Dockerfile, docker-compose.yml, .dockerignore |
| Build systems | Makefile, build scripts, bundler configs |
| Shell scripts | .sh files, deployment scripts, setup scripts |
| Infrastructure as Code | Terraform, CloudFormation, Pulumi |
| Package/dependency config | Complex package.json scripts, pyproject.toml build sections |
| Environment config | .env templates, secrets management patterns |
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 · 132 lines · 42 tokens per session scan A 0275c2706e09
pact-devops-engineer is an agent published in the GitHub repository Synaptic-Labs-AI/PACT-Plugin (71 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 1,670 once invoked, about $0.0002 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
deployment-engineer
Use this agent when you need to set up CI/CD pipelines, containerize applications, configure cloud deployments, or automate infrastructure. This includes creating GitHub Actions workflows, writing Dockerfiles, setting up Kubernetes deployments, implementing infrastructure as code, or establishing deployment…
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.
engineering-devops-automator
DevOps自动化工程师，负责CI/CD流水线设计、Docker容器化部署、基础设施即代码(IaC)、监控告警配置，确保项目从构建到部署的全链路自动化.
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.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.