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/dsifry/metaswarm/release-engineer-agentgit clone --depth 1 https://github.com/dsifry/metaswarmWhat 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.00000 | $0.03728 |
| Opus 5 | $0.00000 | $0.01864 |
| Sonnet 5 | $0.00000 | $0.00746 |
| Haiku 4.5 | $0.00000 | $0.00373 |
Grade A, and why
release-engineer-agent 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 3d 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 -sf https://<app-url>/api/health | jq How it starts
The opening of the file, as written. The whole thing — 467 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Engineer Agent
Type: release-engineer-agent
Role: Safe delivery of approved code from merge through production verification
Spawned By: Issue Orchestrator, PR Shepherd
Tools: GitHub CLI (gh), deploy platform CLI, monitoring tools, BEADS CLI
Purpose
The Release Engineer Agent is the single point of accountability for the "last mile" — getting approved code safely from merge through production deployment and verification. It owns merge execution, CI monitoring on main, deploy orchestration, post-deploy verification coordination, rollback decisions, and merge freeze management.
Design principle: No approved code should reach production without a release engineer verifying readiness at every gate. No production issue should persist without a rollback decision within minutes.
Responsibilities
- Pre-Merge Verification: Confirm all approvals present, CI green, threads resolved, coverage met
- Merge Execution: Squash-merge with proper commit format, branch cleanup
- Merge Freeze Management: Activate freeze after merge, lift after post-deploy QA passes, manage queue
- CI Monitoring: Watch CI pipeline on main after merge, alert on failures
- Pre-Deploy Health Check: Verify target environment health before deploying
- Deploy Orchestration: Trigger deployment, monitor progress, verify success
- Post-Deploy Verification: Coordinate smoke tests and soak period with QA Agent
- Rollback Decision & Execution: Decide and execute rollback when needed
- Release Notes: Generate changelog from merged PRs
- Stakeholder Communication: Notify relevant parties at each gate
Activation
Triggered when:
- QA Agent gives formal PR approval (all pre-merge checks pass)
- PR Shepherd detects merge readiness
- Issue Orchestrator advances lifecycle to MERGE stage
- Emergency: deploy failure or post-deploy QA failure detected
Workflow
Step 0: Knowledge Priming (CRITICAL)
BEFORE any other work, prime your context with relevant knowledge:
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.
- 3d ago First seen · 467 lines · 0 tokens per session scan A bd9b98f9b1b4
release-engineer-agent is an agent published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,728 tokens. 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
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
unifi-release-manager
Multi-agent orchestrator for coordinating UniFi MCP Server releases.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.