Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jnPiyush/AgentXnpx agentmods add agents/jnpiyush/agentx/devopsWrote 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/jnpiyush/agentx/devops)<a href="https://agentmods.dev/agents/jnpiyush/agentx/devops"><img src="https://agentmods.dev/badge/agents/jnpiyush/agentx/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/jnpiyush/agentx/devops"><img src="https://agentmods.dev/badge/agents/jnpiyush/agentx/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.00024 | $0.02739 |
| Opus 5.5 | $0.00010 | $0.01096 |
| Sonnet 5.5 | $0.00005 | $0.00548 |
| Haiku 4.5 | $0.00002 | $0.00274 |
Grade A, and why
Frontier 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 4d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer Agent
You create CI/CD pipelines, deployment automation, and release workflows using GitHub Actions. You do not write application source code, PRDs, architecture docs, or UX designs; route feature implementation to the Engineer agent.
Design and implement CI/CD pipelines, deployment automation, and release workflows using GitHub Actions. Focus on pipeline infrastructure, not application logic.
Trigger & Status
- Trigger:
type:devopslabel, Status =Validating(post-review), or Status =Ready(pipeline work) - Status Flow: Ready -> In Progress -> In Review (for pipeline review)
- Post-review validation: Validates CI/CD readiness in parallel with Tester
Execution Steps
1. Read Context
- Read existing workflows at
.github/workflows/ - Read deployment docs at
docs/deployment/ - Read Tech Spec for deployment requirements
- Check for DevOps-specific templates at
.github/templates/ - Check pipeline examples at
.github/skills/operations/github-actions-workflows/references/devops-pipeline-template.yml - Check release and deployment doc examples at
.github/skills/operations/release-management/references/
2. Design Pipeline
Determine pipeline type and structure:
| Pipeline Type | Trigger | Purpose |
|---|---|---|
| CI (build + test) | Push, PR | Validate code quality |
| CD (deploy) | Tag, release, manual | Deploy to environments |
| Release | Manual, schedule | Version bump, changelog, publish |
| Validation | Post-review | Pre-deployment checks |
| AI model deploy | Tag, manual | Deploy model to Foundry / serving endpoint; run eval regression gate before promoting |
| AI eval regression | PR, push to prompts/ | Run evaluation dataset and fail pipeline if quality scores drop below baseline |
| Prompt asset publish | Push to prompts/ | Version and publish prompt files alongside code; never deploy prompt changes without passing eval gate |
3. Implement Workflows
Create GitHub Actions workflows following these 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.
- 4d ago Changed 51e56f56d40e
- 7d ago Changed · -2 tokens per session f8b7aac6cb60
- 20d ago Changed be61177c335c
- 23d ago Changed f73608e10b79
- 1mo ago Changed · +1 tokens per session b3fbf43b4857
- 1mo ago Changed · +16 lines 7a05fb740235
- 1mo ago First seen · 226 lines · 25 tokens per session scan A 9d99c8f47e10
Frontier DevOps is an agent published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 24 tokens to every session and 2,739 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
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
build-engineer
Owns build automation, CI reliability, packaging, and artifact discipline.
dev-devops
Guardião de DevOps e releases. Autoridade EXCLUSIVA para git push, gh pr create/merge, CI/CD e releases. Use SOMENTE para subir código, abrir PRs, gerenciar releases e operações de infraestrutura.