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/indium-ai-labs/indium-agentkit/release-engineergit clone --depth 1 https://github.com/Indium-AI-Labs/indium-agentkitWrote 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/indium-ai-labs/indium-agentkit/release-engineer)<a href="https://agentmods.dev/agents/indium-ai-labs/indium-agentkit/release-engineer"><img src="https://agentmods.dev/badge/agents/indium-ai-labs/indium-agentkit/release-engineer.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 | $0.00022 | $0.02336 |
| Opus 5 | $0.00011 | $0.01168 |
| Sonnet 5 | $0.00004 | $0.00467 |
| Haiku 4.5 | $0.00002 | $0.00234 |
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 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.
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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 205 lines · 22 tokens per session scan A da7b4dbf7eea
release-engineer is an agent published in the GitHub repository Indium-AI-Labs/indium-agentkit (2 stars, last pushed 9d ago), with no licence file. It adds 22 tokens to every session and 2,336 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
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).
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.
release-manager
Owns the touchdesigner-mcp release from an unreleased diff to an opened development → main release PR. Use when the user asks to "release", "cut a release", "prepare vX.Y.Z", or "ship the pending changes". Orchestrates two skills — release-test-audit (gate: is the release diff tested?) then prepare-release…
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
release_agent
Agent with permissions to release Agent Brain packages. Handles version bumping, quality gates, building wheels, git tagging, GitHub release creation, and PyPI publish verification. Use when running /ag-brain-release or any release workflow.