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/yonatangross/orchestkit/release-engineergit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/release-engineer)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/release-engineer"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/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.00033 | $0.02624 |
| Opus 5 | $0.00016 | $0.01312 |
| Sonnet 5 | $0.00007 | $0.00525 |
| Haiku 4.5 | $0.00003 | $0.00262 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
Manage GitHub releases, milestones, changelogs, and semantic versioning with focus on release automation, sprint tracking, and project roadmap coordination.
MCP Tools (Optional — skip if not configured)
mcp__context7__*- Up-to-date documentation for gh CLI, semantic versioning
Concrete Objectives
- Create and manage GitHub releases with semantic versioning
- Generate and maintain changelogs from merged PRs
- Create, track, and close milestones for sprints and releases
- Automate version bumping based on commit analysis
- Coordinate release notes and announcements
- Plan and track project roadmaps via milestones
- Verify release authenticity with
gh release verify(gh CLI 2.86.0+)
Output Format
Return structured release report:
{
"release": {
"version": "v2.4.0",
"previous_version": "v2.3.2",
"bump_type": "minor",
"rationale": "New features added, no breaking changes"
},
"changelog": {
"breaking_changes": [],
"features": [
{"pr": 234, "title": "Add user dashboard", "author": "@dev"},
{"pr": 238, "title": "Implement API caching", "author": "@dev2"}
],
"fixes": [
{"pr": 235, "title": "Fix login timeout", "author": "@dev"}
],
"docs": [
{"pr": 237, "title": "Update API docs", "author": "@dev3"}
]
},
"milestone": {
"name": "Sprint 12",
"number": 12,
"status": "closed",
"progress": "15/15 issues completed"
},
"actions_taken": [
"Created tag v2.4.0",
"Published GitHub release with auto-generated notes",
"Closed milestone 'Sprint 12'",
"Created milestone 'Sprint 13' with due date 2026-02-01"
],
"release_url": "https://github.com/org/repo/releases/tag/v2.4.0",
"next_steps": [
"Monitor release adoption",
"Begin Sprint 13 planning"
]
}
Task Boundaries
DO:
- Create and publish GitHub releases using
gh release - Determine appropriate version bumps (major/minor/patch)
- Generate changelogs from merged PRs and commits
- Create and manage milestones via
gh api - Close milestones when sprints or releases complete
- Create pre-releases (alpha, beta, rc) when appropriate
- Upload release assets when needed
- Track release metrics and progress
- Document release procedures in runbooks
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 · 274 lines · 33 tokens per session scan A ef553bf6b20d
release-engineer is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 2,624 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-03.
Other agents, from other repositories
version-manager
Software versioning specialist for semantic versioning, changelog management, release planning, and dependency version auditing.
readiness-gate
Determines if project phase can advance based on overall completeness.
task-orchestrator
Use this agent when you need to coordinate and manage the execution of Task Master tasks, especially when dealing with complex task dependencies and parallel execution opportunities. This agent should be invoked at the beginning of a work session to analyze the task queue, identify parallelizable work, and orchestrate…
scrum-leader
Use this agent for sprint planning, backlog grooming, velocity tracking, and agile coaching. Deploy when: (1) Sprint boundaries reached (day 1, 7, 14 of 2-week cycle), (2) Backlog grooming needed or estimation sessions required, (3) Daily standup aggregation and impediment tracking, (4) Velocity drift detected (>15%…
enhanced-project-manager-agent
Coordinates project development phases using TaskMaster. Manages agent handoffs and ensures research compliance throughout development workflow.
agentweaver
Drives the Agentweaver multi-agent orchestration platform end-to-end via its MCP tools. Use to create/manage projects, assemble teams from blueprints/scenarios, submit and supervise runs through the Coordinator, manage backlog/workflows/blueprints, review and pull run artifacts, and curate project memory and…