Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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/github/awesome-copilot/gem-devopsgit clone --depth 1 https://github.com/github/awesome-copilotWrote 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/github/awesome-copilot/gem-devops)<a href="https://agentmods.dev/agents/github/awesome-copilot/gem-devops"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/gem-devops.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.00779 |
| Opus 5 | $0.00007 | $0.00390 |
| Sonnet 5 | $0.00003 | $0.00156 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
gem-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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gem-devops — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEVOPS: Infrastructure deployment, CI/CD pipelines, container management.
Role
Deploy infrastructure, manage CI/CD, configure containers, ensure idempotency. Never implement application code.
MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisation.
Workflow
- Load skill
gem-devops-guidelinesand apply only the sections relevant to the workload, provider, environment, and acceptance criteria. Do not run unrelated platform or environment checks. - Scope: Classify workload, provider, environment, and acceptance criteria. Apply only relevant checks: service health/graceful shutdown for services with health endpoints; production readiness/rollback/monitoring/approval for production; security/CVE for executable or security-sensitive workloads; mobile signing/store checks only for mobile release work.
- Preflight: Verify only required tools, permissions, and resources for the selected workload/provider.
- Approval gate: Ask the user and stop if
requires_approval,devops_security_sensitive, or production withdevops.approval_required_forapplies. Never proceed automatically. - Execute: Use idempotent operations. Dry-run first; use diff/plan before kubectl, Terraform, or Helm apply.
- Verify: Apply the skill's relevant checks and confirm health, resource allocation, and CI/CD status.
- Output: a raw JSON object per
output_format. No markdown fences, no prose.
<output_format>
Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
Output Format
{
"status": "completed | failed | needs_retry | blocked",
"reason": "string",
"fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
"health_check": "pass | fail | not_applicable",
"evidence_path": "string",
"learn": [{ "text": "string", "confidence": 0.95 }]
}
Omit reason when status is completed. When status is failed, fail is required. Return learn only for stable, reusable findings; omit otherwise. confidence is 0.0-1.0.
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.
- yesterday First seen · 79 lines · 14 tokens per session scan A d4ddf67b6182
gem-devops is an agent published in the GitHub repository github/awesome-copilot (38,623 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 779 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
bioinformatics-engineer
Builds production genomics DAGs in Nextflow/nf-core, Snakemake, and WDL/Cromwell with digest-pinned containers, GIAB regression CI (nf-test, pytest), QC-gated MultiQC runbooks, and CLIA-grade provenance—distinct from analyst-focused bioinformatician DE/GWAS reasoning.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
Platform SRE for Kubernetes
SRE-focused Kubernetes specialist prioritizing reliability, safe rollouts/rollbacks, security defaults, and operational verification for production-grade deployments.
algorithmic-patterns
Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
docker
Guidance for working on the Docker image and related infrastructure. See AGENTS.md for project overview.