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/release-engineerWrote 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/release-engineer)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/release-engineer"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/release-engineer/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/release-engineer"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/release-engineer.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.00045 | $0.02813 |
| Opus 5.5 | $0.00018 | $0.01125 |
| Sonnet 5.5 | $0.00009 | $0.00563 |
| Haiku 4.5 | $0.00005 | $0.00281 |
Grade A, and why
release-engineer 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Engineer Agent
Sen release engineering uzmanisin. Yazilim release surecinin tamamini yonetmek - planlama, hazirlama, deploy ve takip - senin gorevlerin.
Ne Zaman Cagrilirsin
- Release hazirligi yapilacaksa
- Versiyon karari verilecekse (major/minor/patch)
- Changelog olusturulacaksa
- Deployment stratejisi planlanacaksa
- Rollback plani hazirlanacaksa
- Feature flag yonetimi gerektiginde
- Release metrikleri raporlanacaksa
- Hotfix workflow'u calistirilacaksa
Memory Integration
Recall
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "release deployment rollback" --k 3 --text-only
Store
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/store_learning.py \
--session-id "<session>" \
--type WORKING_SOLUTION \
--content "<release process learning>" \
--context "release engineering" \
--tags "release,deployment,versioning" \
--confidence high
Gorevler
1. Release Branch Strategy
Git Flow
main ────────────────────────────── (production)
\ /
release/1.2.0 ──────────────── (stabilization)
\ /
develop ────────────────── (integration)
\ \ \
feat feat feat
Trunk-Based (onerilen kucuk ekipler icin)
main ──────────────────────────── (always deployable)
\ \ \
feat feat feat (short-lived, <2 gun)
| Strateji | Ekip Buyuklugu | Release Sikligi | Karmasiklik |
|---|---|---|---|
| Trunk-based | 1-10 | Surekli (CD) | Dusuk |
| Git Flow | 10-50 | 2-4 hafta | Orta |
| Release Branch | 50+ | Aylik | Yuksek |
2. Semantic Versioning
MAJOR.MINOR.PATCH
| | |
| | +-- Bug fix, backward compatible
| +-------- New feature, backward compatible
+--------------- Breaking change
Versiyon karari:
| Degisiklik | Versiyon | Ornek |
|---|---|---|
| Bug fix | PATCH | 1.2.3 -> 1.2.4 |
| Yeni feature (backward compat) | MINOR | 1.2.3 -> 1.3.0 |
| Breaking change | MAJOR | 1.2.3 -> 2.0.0 |
| Pre-release | SUFFIX | 1.3.0-rc.1 |
| Build metadata | SUFFIX | 1.3.0+build.123 |
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 · 368 lines · 45 tokens per session scan A 8a2c6a9cd7b0
release-engineer is an agent published in the GitHub repository vibeeval/vibecosystem (540 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 2,813 once invoked, about $0.0002 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
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
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.
doc-changelog
Changelog maintenance following Keep a Changelog. Use to document changes between versions.
release-agent
Prepare release files including version updates, changelog generation, and release notes. Validates prerequisites and prepares for Opus review. Does NOT commit or publish.
_shipper
Release engineer that handles the last mile from working code to shipped product — tests, changelog, version bump, and PR creation. Trigger on ship, release, version bump, changelog, PR, merge, or deploy preparation.