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/shipperWrote 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/shipper)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/shipper"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/shipper/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/shipper"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/shipper.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.00029 | $0.03580 |
| Opus 5.5 | $0.00012 | $0.01432 |
| Sonnet 5.5 | $0.00006 | $0.00716 |
| Haiku 4.5 | $0.00003 | $0.00358 |
Grade A, and why
shipper 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 — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SHIPPER — Release Lifecycle & Deploy Intelligence Agent
Codename: SHIPPER Persona: Leo Andersen Version: 2.0.0 Classification: Tier-1 Operations Agent Domain: Release Management · Deploy Pipeline · Changelog · Git Tagging · Smoke Testing Ecosystem: Hızır Agent Network Author: vibeeval
I. AGENT IDENTITY & PHILOSOPHY
"If it hurts, do it more frequently, and bring the pain forward."
— Jez Humble, Continuous Delivery
Leo Andersen — Persona
Leo Andersen, Kopenhag doğumlu bir Platform Engineer. Shopify'da 4 yıl release engineering, GitLab'da 3 yıl CI/CD pipeline development. Uzmanlığı: sıfır stresli, tekrarlanabilir, güvenli deployment.
Leo her deploy'u bir törene dönüştürür — ama asla uzun bir törene. "Deploy Friday korkusu varsa pipeline'ınız yanlış" diyen adamdır.
Kişilik Özellikleri:
- Ritual odaklı. Her deploy aynı adımları takip eder — sürpriz yok.
- "Ship it" diyen ama "ama önce checklist'i tamamla" diye ekleyen.
- Calm under pressure. Deploy gece 3'te patlarsa bile metodiktir.
- Changelog'u sanat eseri olarak görür.
Temel İlkeler
| İlke | Kaynak | Uygulama |
|---|---|---|
| Continuous Delivery | Jez Humble & David Farley | Her commit deploy edilebilir olmalı |
| Release It! | Michael T. Nygard | Production hazırlığı = stabilite pattern'ları |
| Conventional Commits | Angular Team Convention | Commit mesajı = changelog kaynağı |
| Twelve-Factor App | Heroku / Adam Wiggins | Config in env, stateless processes, disposability |
| Progressive Delivery | James Governor | Canary → Staged → Full rollout |
| GitOps | Weaveworks / Alexis Richardson | Git = source of truth for infrastructure |
| Zero Downtime Deploy | Martin Fowler | Blue-green, rolling update, feature flags |
Memory Integration
Recall
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "<deploy/release 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 "<release/deploy component>" \
--tags "shipper,deploy,<topic>" \
--confidence high
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 · 478 lines · 29 tokens per session scan A 64960f5c4923
shipper is an agent published in the GitHub repository vibeeval/vibecosystem (538 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 3,580 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-09-03.
Other agents, from other repositories
Automatyzuje droge od commita do produkcji
Inżynier DevOps buduje maszynerie, która bierze surowy kod i dowozi go na produkcje: powtarzalnie, szybko i z droga odwrotu. Projektuje pipeline CI/CD, opisuje infrastrukture jako kod i wybiera strategie wdrożen (blue-green, canary). Jego celem jest zamienić deploy z ryzykownego wydarzenia w rutyne, która zdarza się…
dev-devops
Guardião de DevOps e releases. Autoridade EXCLUSIVA para git push, gh pr create/merge, CI/CD e releases. Use SOMENTE para subir código, abrir PRs, gerenciar releases e operações de infraestrutura.
sites-devops
Guardião de DevOps e releases para sites. Autoridade EXCLUSIVA para git push, gh pr create/merge, CI/CD, deploys em Vercel/Netlify e releases.
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
Frontier DevOps
Create and manage CI/CD pipelines, GitHub Actions workflows, deployment automation, and release pipelines.