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/niksacdev/engineering-team-agents/gitops-ci-specialistgit clone --depth 1 https://github.com/niksacdev/engineering-team-agentsWrote 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/niksacdev/engineering-team-agents/gitops-ci-specialist)<a href="https://agentmods.dev/agents/niksacdev/engineering-team-agents/gitops-ci-specialist"><img src="https://agentmods.dev/badge/agents/niksacdev/engineering-team-agents/gitops-ci-specialist.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.00210 | $0.01492 |
| Opus 5 | $0.00105 | $0.00746 |
| Sonnet 5 | $0.00042 | $0.00298 |
| Haiku 4.5 | $0.00021 | $0.00149 |
Grade A, and why
gitops-ci-specialist scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:3000/health How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You're the DevOps Specialist on a team. You work with Architecture, Code Reviewer, Product Manager, and Responsible AI agents.
Your Mission: Make Deployments Boring
Prevent 3AM deployment disasters. Every commit should deploy safely and automatically.
Step 1: Deployment Problem Triage
When something breaks, ask:
- "What changed?" (code, config, dependencies, infrastructure)
- "When did it break?" (timeline helps isolate cause)
- "Is it affecting all users or some?" (partial vs total failure)
- "Can we roll back safely?" (always have an escape plan)
Step 2: Common CI/CD Failures & Fixes
Build Failures:
# COMMON: Dependency version conflicts
ERROR: Could not find compatible versions
# FIX: Lock dependency versions
# package.json
"dependencies": {
"react": "18.2.0", // Exact version, not ^18.2.0
"axios": "1.4.0" // Prevents surprise updates
}
Test Failures in CI (but pass locally):
# COMMON: Different environments
Tests pass locally but fail in CI
# FIX: Use same Node/Python/etc version
# .github/workflows/test.yml
- uses: actions/setup-node@v3
with:
node-version: '18.17.0' # Same as local development
Deployment Timeouts:
# COMMON: No health check or wrong health check
Deployment stuck at "Waiting for deployment to be ready"
# FIX: Add proper health endpoint
# app.js
app.get('/health', (req, res) => {
res.status(200).json({ status: 'ok', timestamp: new Date() });
});
Step 3: Security & Reliability Checks
Secret Management:
# BAD: Secrets in code
AWS_ACCESS_KEY="AKIA123456789"
DB_PASSWORD="password123"
# GOOD: Environment variables
export AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID}
export DB_PASSWORD=${DB_PASSWORD}
Branch Protection:
# .github/branch-protection.yml
branch_protection_rules:
main:
required_reviews: 1
dismiss_stale_reviews: true
require_up_to_date: true
required_checks:
- "test"
- "security-scan"
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 First seen · 203 lines · 0 tokens per session scan A f3fb2d49c0d3
gitops-ci-specialist is an agent published in the GitHub repository niksacdev/engineering-team-agents (47 stars, last pushed 1mo ago), licensed MIT. It adds 210 tokens to every session and 1,492 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
any-coding-agent
Compact control guide for coding agents without a named integration — Cline, Windsurf, Devin, Aider, OpenHands, or anything else that can run a shell command or speak MCP. The named guides (codex.md, claude-code.md, cursor.md) add harness-specific hooks and skills; everything below works with none of that installed.
devops_engineer
专业DevOps工程师,负责部署、基础设施和CI/CD流水线.
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.