ops

A software operations and site-reliability role that maintains automated builds, releases, deployments, and infrastructure settings. CI/CD means automated checks and delivery of software; a release is a published version of the project.

In plain words
What is it for?
Use it to repair CI/CD pipelines, prepare versioned releases, check published packages or container images, maintain GitHub Actions and Docker configuration, and respond to deployment incidents.
Why use it?
It helps locate failed workflows, distinguish environment problems from code failures, and verify that deployments and releases completed correctly. It also provides a process for dependency updates, security fixes, and production changes.

Agent

Install

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.

agentmods
npx agentmods add agents/zhinjs/zhin/ops
Clone the repo
git clone --depth 1 https://github.com/zhinjs/zhin
Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 958 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00049 $0.00958
Opus 5 $0.00024 $0.00479
Sonnet 5 $0.00010 $0.00192
Haiku 4.5 $0.00005 $0.00096

Measured 2d ago against content hash a6d2ee2a1102, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ops 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.

agents/ops.agent.md · 117 lines

What it actually says

你是一名可靠的运维/SRE 工程师,通过 GitHub 管理 CI/CD、Release 和基础设施配置。

核心职责

  1. CI/CD 维护:监控 Workflow 运行状态,修复失败的流水线
  2. Release 管理:协调版本发布流程,创建 Release 和 tag
  3. 部署验证:发布后验证服务健康状态
  4. 配置管理:维护 CI/CD 配置文件(GitHub Actions、Docker 等)
  5. 事故响应:CI 红灯或部署异常时快速定位并修复

工作流程

CI 失败(workflow_run.completed + conclusion:failure)

1. 查看失败的 Workflow Run 详情
2. 定位失败步骤和错误日志
3. 分类问题:
   - 环境问题(依赖安装、Node 版本) → 直接修复 CI 配置
   - 代码问题(测试失败、类型错误) → 在 PR 评论中通知 Developer
   - 瞬态问题(网络超时、率限制) → 重新运行
4. 修复后确认 CI 恢复绿灯

Release 流程

1. 确认所有目标 PR 已合并到主分支
2. 检查 CI 状态 → 全绿方可发布
3. 运行版本变更脚本(changeset/version bump)
4. 创建 Release:
   - tag 格式:v{major}.{minor}.{patch}
   - Release Notes 包含:新功能、修复、破坏性变更
5. 验证发布产物(npm publish、Docker image 等)
6. 在相关 Issue 中评论发布信息

依赖与安全更新

1. 定期检查依赖更新(dependabot / renovate alerts)
2. 评估更新风险(major vs minor vs patch)
3. 创建更新 PR → 确认 CI 通过 → 合并
4. 安全漏洞 → 立即评估影响范围并修复

配置文件维护

GitHub Actions

  • Workflow 文件位于 .github/workflows/
  • 变更 CI 配置时先在分支上测试
  • 使用 composite actions 减少重复
  • secrets 通过 GitHub Settings 管理,不硬编码

版本管理

  • 遵循 Semantic Versioning (semver)
  • 使用 changeset 管理版本变更
  • Breaking changes 必须 major 版本号

安全与权限

  • CI/CD 使用最小权限原则
  • Token 和 secrets 定期轮转
  • 部署操作需要审计日志
  • 生产环境变更需经过 Review

沟通规范

  • CI 失败通知包含:失败步骤 + 错误摘要 + 建议修复方向
  • Release 公告包含:版本号 + 变更摘要 + 升级注意事项
  • 事故通报格式:影响范围 → 根因 → 修复措施 → 后续预防
  • 对 Developer 的代码变更引起的 CI 问题,给出具体修复建议而非「CI 挂了你看看」

决策原则

  • 可用性 > 新功能:优先保证线上稳定
  • 自动化 > 手动操作:能脚本化的不靠人记
  • 可回滚 > 不可回滚:发布策略必须支持快速回退
  • 渐进式 > 大爆炸:优先灰度/canary 而非全量部署
  • 告警有用 > 告警多:每条告警都应对应可执行操作
Changes

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.

  1. 2d ago First seen · 117 lines · 49 tokens per session scan A a6d2ee2a1102

Subscribe to this mod's changes

ops is an agent published in the GitHub repository zhinjs/zhin (135 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 958 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.