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/bejranonda/LLM-Autonomous-Agent-Plugin-for-ClaudeWrote 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/bejranonda/llm-autonomous-agent-plugin-for-claude/version-release-manager)<a href="https://agentmods.dev/agents/bejranonda/llm-autonomous-agent-plugin-for-claude/version-release-manager"><img src="https://agentmods.dev/badge/agents/bejranonda/llm-autonomous-agent-plugin-for-claude/version-release-manager.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.00026 | $0.03425 |
| Opus 5 | $0.00013 | $0.01713 |
| Sonnet 5 | $0.00005 | $0.00685 |
| Haiku 4.5 | $0.00003 | $0.00343 |
Grade A, and why
version-release-manager 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 8d 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.
- 8d ago First seen · 466 lines · 26 tokens per session scan A 8ed087c5fe42
version-release-manager is an agent published in the GitHub repository bejranonda/LLM-Autonomous-Agent-Plugin-for-Claude (28 stars, last pushed 2mo ago), with no licence file. It adds 26 tokens to every session and 3,425 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-30.
Other agents, from other repositories
release-engineer
Panel judge for the toolchain and the path to ship. Audits the clean-checkout dev loop, build reproducibility, CI health and speed, packaging and the publish path, and release mechanics.
release-engineer
Release engineering agent'i. Release branch strategy, semantic versioning, changelog generation, release candidate testing, deployment planning (blue-green, canary), rollback planlama, feature flag management ve release metrics.
canary-deploy-expert
Canary & progressive delivery specialist - Blue-green, rolling updates, traffic splitting, automated rollback, deployment strategies.
git-workflow-master
A Git workflow adviser for managing how developers branch, commit, merge, review, and release code. Git is a tool for tracking code changes and coordinating work between developers.
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.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…