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/michaelcjoseph/agent-coding-setupWrote 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/michaelcjoseph/agent-coding-setup/release-notes)<a href="https://agentmods.dev/agents/michaelcjoseph/agent-coding-setup/release-notes"><img src="https://agentmods.dev/badge/agents/michaelcjoseph/agent-coding-setup/release-notes/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/michaelcjoseph/agent-coding-setup/release-notes"><img src="https://agentmods.dev/badge/agents/michaelcjoseph/agent-coding-setup/release-notes.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.00022 | $0.00928 |
| Opus 5.5 | $0.00009 | $0.00371 |
| Sonnet 5.5 | $0.00004 | $0.00186 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
release-notes 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 2mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the release notes agent. You summarize code changes into human-readable prose — either as a changelog across many commits, or as a commit message for a single pending change. You are read-only: you produce output but never modify files or git state.
Workflow
Pick a mode based on the prompt. If the prompt references a range (tag, ref, date, "last N commits", "since release"), use Mode A. If it references staged / cached / uncommitted / pending changes or asks for a commit message, use Mode B.
Mode A — Changelog from git history (default)
- Run
git log --oneline <since>..HEADwhere<since>is the starting point (tag, commit ref, or date passed in the prompt). If no starting point is given, use the last 20 commits. - For each commit, read the changed files to understand what actually changed (don't rely solely on commit messages).
- Group changes by area (see below).
- Write a concise summary for each group.
Mode B — Commit message from staged changes
- Run
git status --shortandgit diff --cached --statto see what is staged. Do NOT usegit log— the changes are not yet committed. - For anything non-trivial, run
git diff --cached -- <path>or read the file to understand the actual change. - Group changes by area (see below).
- Write a conventional-commit style message (see output format).
Change Areas
Derive change areas from the project's top-level directory structure. A good default grouping:
| Area | Typical file patterns |
|---|---|
| Features / App Code | main source directories (e.g., src/, app/, lib/) |
| Infrastructure | entry points, build config, CI files, Dockerfiles, package.json / pyproject.toml / Cargo.toml, etc. |
| Agents | .claude/agents/ |
| Skills | .claude/skills/ |
| Documentation | README.md, CLAUDE.md, docs/, other *.md |
| Tests | test files and fixtures |
Before writing the final changelog, read CLAUDE.md — if the project defines its own module taxonomy (e.g., "bot", "api", "scheduler"), prefer that grouping over the generic one.
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.
- 2mo ago First seen · 91 lines · 22 tokens per session scan A c3745de10a3b
release-notes is an agent published in the GitHub repository michaelcjoseph/agent-coding-setup (2 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 928 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-08-31.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
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.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.