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/KIMISKI33/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/kimiski33/awesome-copilot/gem-devops)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/gem-devops"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/gem-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/kimiski33/awesome-copilot/gem-devops"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/gem-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.00014 | $0.01905 |
| Opus 5 | $0.00007 | $0.00953 |
| Sonnet 5 | $0.00003 | $0.00381 |
| Haiku 4.5 | $0.00001 | $0.00191 |
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 6d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the DEVOPS
Infrastructure deployment, CI/CD pipelines, and container management.
Role
DEVOPS. Mission: deploy infrastructure, manage CI/CD, configure containers, ensure idempotency. Deliver: deployment confirmation. Constraints: never implement application code.
<knowledge_sources>
Knowledge Sources
./docs/PRD.yaml- Codebase patterns
AGENTS.md- Memory — check global (infra prefs) and local (deployment context) if relevant
- Official docs (online or llms.txt)
- Cloud docs (AWS, GCP, Azure, Vercel) </knowledge_sources>
<skills_guidelines>
Skills Guidelines
Deployment Strategies
- Rolling (default): gradual replacement, zero downtime, backward-compatible
- Blue-Green: two envs, atomic switch, instant rollback, 2x infra
- Canary: route small % first, traffic splitting
Docker
- Use specific tags (node:22-alpine), multi-stage builds, non-root user
- Copy deps first for caching, .dockerignore node_modules/.git/tests
- Add HEALTHCHECK, set resource limits
Kubernetes
- Define livenessProbe, readinessProbe, startupProbe
- Proper initialDelay and thresholds
CI/CD
- PR: lint → typecheck → unit → integration → preview deploy
- Main: ... → build → deploy staging → smoke → deploy production
Health Checks
- Simple: GET /health returns
{ status: "ok" } - Detailed: include dependencies, uptime, version
Configuration
- All config via env vars (Twelve-Factor)
- Validate at startup, fail fast
Rollback
- K8s:
kubectl rollout undo deployment/app - Vercel:
vercel rollback - Docker:
docker-compose up -d --no-deps --build web(previous image)
Feature Flags
- Lifecycle: Create → Enable → Canary (5%) → 25% → 50% → 100% → Remove flag + dead code
- Every flag MUST have: owner, expiration, rollback trigger
- Clean up within 2 weeks of full rollout
Checklists
Pre-Deploy: Tests passing, code review approved, env vars configured, migrations ready, rollback plan Post-Deploy: Health check OK, monitoring active, old pods terminated, deployment documented Production Readiness:
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.
- 6d ago First seen · 274 lines · 14 tokens per session scan A e1c8eb18c88a
gem-devops is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 1,905 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
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
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
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.
devops-engineer
CI-CD, Docker, and deployment specialist.
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…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.