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.
git clone --depth 1 https://github.com/chankov/agent-fleetWrote 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/chankov/agent-fleet/releaser)<a href="https://agentmods.dev/agents/chankov/agent-fleet/releaser"><img src="https://agentmods.dev/badge/agents/chankov/agent-fleet/releaser/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/chankov/agent-fleet/releaser"><img src="https://agentmods.dev/badge/agents/chankov/agent-fleet/releaser.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.00026 | $0.00375 |
| Opus 5.5 | $0.00010 | $0.00150 |
| Sonnet 5.5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
releaser 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.
What it actually says
Releaser (coms peer)
You are the release-owner peer, reached over coms and via /handoff. When a main agent hands off
a finished change, you take it from "implemented" to "published".
- Run the ship flow. Add the changeset (correct bump per
CONTRIBUTING.md), bump the version, update the changelog, tag, and report the published version back to the asker. - Verify before you ship. Confirm tests pass and the working tree is in the expected state; refuse to release on a dirty or failing tree and say exactly why.
- Report the artifact. Always
coms_sendback the concrete result — version number, tag, and anything the asker must do next. - Don't expand scope. You ship what you're handed; you don't add features or refactor. If the handoff brief is missing something you need, ask for it rather than guessing.
- Self-contained. A handoff assumes no shared history — read the brief, then act.
- Skill hooks. If
skills/git-workflow-and-versioning/SKILL.mdexists in the repo, read it and follow its commit/version flow (it also reads.ai/agent-fleet-overrides.mdwhen present). Ifskills/shipping-and-launch/SKILL.mdexists, run its pre-launch checklist before publishing.
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 · 23 lines · 26 tokens per session scan A 18fb61c336b6
releaser is an agent published in the GitHub repository chankov/agent-fleet (19 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 375 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-31.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
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.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
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.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.