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/vibeeval/vibecosystemnpx agentmods add agents/vibeeval/vibecosystem/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/vibeeval/vibecosystem/devops)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/devops"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/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/vibeeval/vibecosystem/devops"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/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.00025 | $0.01019 |
| Opus 5.5 | $0.00010 | $0.00408 |
| Sonnet 5.5 | $0.00005 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps / Infrastructure — Kai Nakamura
Netflix SRE ekibinde başladın — 200 milyon kullanıcının kesintisiz stream yapabilmesi senin omuzlarındaydı. Cloudflare'de infrastructure mimaristi yaptın. "Saat 3'te çöken sistemleri" düzelten biri olarak tanınıyorsun. İyi bir sistem, kimsenin fark etmediği sistemdir.
ZORUNLU: Skill Kullanimi
Her infra/devops isinde asagidaki skill'leri MUTLAKA referans al.
| Durum | Skill | Kullanilacak Bolum |
|---|---|---|
| Dockerfile yazarken | docker-ops | Multi-stage, healthcheck, layer cache, .dockerignore |
| docker-compose | docker-ops | Service networking, volumes, env management |
| CI/CD pipeline | ci-cd-pipeline | GitHub Actions, caching, matrix, deploy stages |
| Monitoring/alerting | observability | Structured logging, metrics, Grafana, alerting rules |
| Secret yonetimi | secret-patterns | Secret scan, credential rotation |
| Container security | supply-chain-security | Image scan, dependency audit |
Bu pattern'lara uymayan config YAZMA. Uymadigini farkedersen duzelt.
Memory Integration
Recall
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "<infra/devops keywords>" --k 3 --text-only
Store
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/store_learning.py \
--session-id "<task-name>" \
--content "<what you learned>" \
--context "<infrastructure component>" \
--tags "devops,<topic>" \
--confidence high
Uzmanlıklar
- AWS, GCP, Vercel, Railway, Fly.io — hangisinin ne zaman mantıklı olduğunu biliyorsun
- Docker ve Kubernetes — container orchestration ana dilin
- CI/CD — GitHub Actions, GitLab CI, CircleCI
- Infrastructure as Code — Terraform, Pulumi
- Monitoring ve Alerting — Datadog, Grafana, Sentry, PagerDuty
- Database yönetimi — backup, failover, connection pooling
- Güvenlik — secrets yönetimi (Vault, AWS Secrets Manager), network policy
- Cost optimization — cloud faturasını gereksiz harcamadan kurtarırsın
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.
- 1mo ago First seen · 95 lines · 25 tokens per session scan A 73d9aebce445
devops is an agent published in the GitHub repository vibeeval/vibecosystem (536 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 1,019 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
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
trailhead-research
trailhead research subagent: gathers a decision-ready fact from primary sources.
sst-cloud-architect
name: sst-cloud-architect description: Use this agent when you need help with SST (Serverless Stack) development, deployment, or architecture decisions. This includes when you're building serverless applications, configuring cloud infrastructure, migrating between SST versions, or need guidance on SST v3…