Borrowing it
Nothing to install: this file belongs to SVerITG/Metis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SVerITG/Metis/main/.claude/agents/release-coordinator.mdgit clone --depth 1 https://github.com/SVerITG/MetisWrote 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/sveritg/metis/release-coordinator)<a href="https://agentmods.dev/agents/sveritg/metis/release-coordinator"><img src="https://agentmods.dev/badge/agents/sveritg/metis/release-coordinator.svg" alt="Measured on agentmods" 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.00043 | $0.00492 |
| Opus 5 | $0.00022 | $0.00246 |
| Sonnet 5 | $0.00009 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
release-coordinator 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 yesterday.
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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- yesterday First seen · 50 lines · 43 tokens per session scan A 05eb0718d1b2
release-coordinator is an agent published in the GitHub repository SVerITG/Metis (3 stars, last pushed yesterday), licensed AGPL-3.0. It adds 43 tokens to every session and 492 once invoked, about $0.0002 per session on Opus 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-05.
Other agents, from other repositories
release-manager
Release manager for Flutter apps handling versioning, changelog management, Fastlane automation, and store submissions to App Store and Google Play. Masters code signing, build configuration, and CI/CD with GitHub Actions.
module-registrar
Register new modules in the Datacore ecosystem. Use this agent: When creating a new module for community contribution For :AI:module:register: tagged tasks To update CATALOG.md with new module entries To create GitHub repos and PRs for module registration Part of the community contribution workflow (DIP-0001).
changelog-generator
Generates changelog from commits.
open-source-maintainer
An open source maintainer who manages community-driven projects — triaging issues, reviewing contributions, writing contribution guidelines, managing releases, and fostering a healthy contributor community. Use for OSS project management, community building, contribution guidelines, and release management.
release-manager
A release manager who coordinates safe, predictable software releases — managing release trains, rollback plans, and cross-team deployment dependencies. Use for release planning, go/no-go decisions, deployment coordination, and rollback strategy.
deploy-admin
GitHub Actions deployment: workflows, releases, GHCR, CI/CD. Triggers: deploy, release.