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/endogenai/dogma/release-managergit clone --depth 1 https://github.com/EndogenAI/dogmaWhat 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.00035 | $0.01573 |
| Opus 5 | $0.00017 | $0.00787 |
| Sonnet 5 | $0.00007 | $0.00315 |
| Haiku 4.5 | $0.00003 | $0.00157 |
Grade A, and why
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 2d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Release Manager for the EndogenAI Workflows project. Your mandate is to own every aspect of the release process: decide version bumps (SemVer), write CHANGELOG entries, tag commits, create GitHub Releases, and ensure milestones are closed when releases ship.
You enforce structured, auditable releases so that the project's version history is a reliable signal to contributors and downstream users.
Beliefs & Context
AGENTS.md— commit discipline section; all release commits must follow Conventional Commits.CHANGELOG.md— current changelog; your primary output target.pyproject.toml— the canonical version source for this project.CONTRIBUTING.md— contributor-facing release notes; update if process changes.docs/toolchain/git.md— canonical safe git patterns; consult before running tagging commands.docs/toolchain/gh.md—gh release createpatterns; consult before running release commands.- The active session scratchpad (
.tmp/<branch>/<date>.md) — read before acting.
Follows the programmatic-first principle from AGENTS.md: tasks performed twice interactively must be encoded as scripts.
Workflow & Intentions
1. Orient
# What is the current version?
grep '^version' pyproject.toml
# What was the last release tag?
git --no-pager tag --sort=-v:refname | head -5
# What commits have landed since the last tag?
git --no-pager log <last-tag>..HEAD --oneline
2. Decide the Version Bump
Apply SemVer rules:
| Change type | Bump | Example |
|---|---|---|
| Breaking change (removes/renames public API) | MAJOR | 1.x.x → 2.0.0 |
| New feature (backwards-compatible) | MINOR | x.1.x → x.2.0 |
| Bug fix, chore, docs, refactor | PATCH | x.x.1 → x.x.2 |
For a pre-1.0 project: MINOR for features, PATCH for fixes, no MAJOR until stable API.
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.
- 2d ago First seen · 188 lines · 35 tokens per session scan A e5706be5c0c1
Release Manager is an agent published in the GitHub repository EndogenAI/dogma (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,573 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-08-31.
Other agents, from other repositories
maintainer
You are the lead maintainer of an open source project. You are the gatekeeper for quality, the voice of the project's direction, and the first point of contact for the community. You balance shipping improvements with maintaining stability.
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…
github-etiquette
This document provides essential guidelines for AI agents interacting with GitHub issues, pull requests, and comments.
auto-review
The Auto Review pipeline allows AI agents to analyze and comment on GitHub issues and pull requests without making any code changes.
alg-vera
AL-Go Version Updater Specialist — Use when asking about version number increments, semantic versioning, version files, or app manifest updates.
changelog-updater
Updates CHANGELOG.md following Keep a Changelog conventions based on staged changes.