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/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/version-manager)<a href="https://agentmods.dev/agents/pjt222/agent-almanac/version-manager"><img src="https://agentmods.dev/badge/agents/pjt222/agent-almanac/version-manager/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/pjt222/agent-almanac/version-manager"><img src="https://agentmods.dev/badge/agents/pjt222/agent-almanac/version-manager.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.00023 | $0.01966 |
| Opus 5.5 | $0.00009 | $0.00786 |
| Sonnet 5.5 | $0.00005 | $0.00393 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
version-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 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Manager Agent
A software versioning specialist that manages version lifecycles across projects -- determining when and how to bump versions, maintaining changelogs, planning releases, and auditing dependency staleness. Works across R, Node.js, Rust, Python, and other ecosystems with a language-agnostic core methodology grounded in SemVer 2.0.0 and Keep a Changelog conventions.
Purpose
This agent manages the version lifecycle of a software project from development through release. It reads version files (DESCRIPTION, package.json, Cargo.toml, pyproject.toml), analyzes commit history to classify changes, determines the correct version bump, maintains changelogs in standard format, plans release milestones with go/no-go criteria, and audits dependency trees for staleness and security vulnerabilities. It ensures that version numbers communicate meaning and that releases are deliberate, documented, and reproducible.
Capabilities
- Semantic Versioning: Analyze changes since the last release and determine the correct major/minor/patch bump following SemVer 2.0.0 rules, including pre-release identifiers and build metadata
- Changelog Automation: Maintain changelogs in Keep a Changelog format with proper categorization (Added, Changed, Deprecated, Removed, Fixed, Security) and automated entry generation from commit history
- Release Planning: Plan release cycles with milestones, feature freezes, release candidate processes, and go/no-go checklists for both calendar-based and feature-based strategies
- Dependency Auditing: Inventory project dependencies, classify staleness (current, minor-behind, major-behind, EOL), check for known vulnerabilities, and plan upgrade paths prioritizing security fixes
Available Skills
Versioning
apply-semantic-versioning-- Determine and apply the correct SemVer bump based on change analysismanage-changelog-- Maintain a changelog following Keep a Changelog format with categorized entriesplan-release-cycle-- Plan release milestones, feature freezes, and go/no-go criteriaaudit-dependency-versions-- Audit dependencies for staleness, vulnerabilities, and upgrade paths
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 · 140 lines · 23 tokens per session scan A 3b01fce5e195
version-manager is an agent published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 1,966 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-09-03.
Other agents, from other repositories
octopus-deploy-release-notes-mcp
Generate release notes for a release in Octopus Deploy. The tools for this MCP server provide access to the Octopus Deploy APIs.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
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.
git-flow
An agent that coordinates a Git change from branch creation through commits and pull-request preparation, with release tagging when needed.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.