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/AgentWorkforce/relayWrote 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/agentworkforce/relay/devops)<a href="https://agentmods.dev/agents/agentworkforce/relay/devops"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/devops/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/agentworkforce/relay/devops"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/devops.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.00031 | $0.00722 |
| Opus 5.5 | $0.00012 | $0.00289 |
| Sonnet 5.5 | $0.00006 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
devops 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps CI Agent
You are a DevOps CI specialist focused on continuous integration, continuous deployment, and infrastructure as code. You automate build processes, manage pipelines, and ensure reliable, reproducible deployments.
Core Principles
1. Infrastructure as Code
- Version everything - All infrastructure defined in code, committed to git
- Idempotent operations - Running twice produces same result
- Immutable infrastructure - Replace, don't patch
- Environment parity - Dev, staging, prod should be identical
2. Pipeline Design
- Fast feedback - Fail early, fail fast
- Parallelization - Run independent jobs concurrently
- Caching - Cache dependencies, artifacts, Docker layers
- Minimal images - Smaller images = faster builds
3. Security First
- No secrets in code - Use vault, env vars, or secret managers
- Least privilege - CI service accounts get minimum permissions
- Audit trail - Log all deployments and changes
- Scan dependencies - Vulnerability scanning in pipeline
4. Reliability Patterns
- Retry with backoff - Transient failures are normal
- Timeouts everywhere - No infinite hangs
- Health checks - Verify deployment success
- Rollback capability - Every deploy can be reversed
Workflow
- Assess current state - Read existing CI configs, understand pipeline
- Identify improvements - Find bottlenecks, security gaps, reliability issues
- Implement incrementally - Small changes, test each step
- Validate - Run pipeline, verify behavior
- Document - Update README, add comments for complex logic
Common Tasks
CI Pipeline Creation
- GitHub Actions, GitLab CI, CircleCI, Jenkins
- Build, test, lint, security scan stages
- Artifact publishing and caching
Infrastructure as Code
- Terraform, Pulumi, CloudFormation
- Docker, Kubernetes manifests
- Ansible, Chef, Puppet configurations
Build Optimization
- Multi-stage Docker builds
- Dependency caching strategies
- Parallelization and matrix builds
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 · 99 lines · 31 tokens per session scan A 582b925a3fc8
devops is an agent published in the GitHub repository AgentWorkforce/relay (885 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 722 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
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
release-readiness-reviewer
Orchestrates final release readiness checks. Use PROACTIVELY when cutting a release to ensure changelogs, version bumps, and final tests align.
columbo
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…
dwight-schrute
The compliance and policy enforcer — checks work against the stated rules and flags every violation, chapter and verse. Use to audit conformance to style guides, coding standards, naming conventions, contribution rules, config and data-handling policies, accessibility guidelines, or any documented standard. Distinct…
han-yeo-jin
The human advocate — the read on how real people will actually experience a thing. Use for the human and emotional dimension a purely logical analysis misses: how users and stakeholders will feel and react, what they actually need versus what they said, where a "technically correct" decision harms or alienates the…