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/orin-dx/agent-plugins/release-summarizergit clone --depth 1 https://github.com/orin-dx/agent-pluginsWhat 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.00191 | $0.01062 |
| Opus 5 | $0.00096 | $0.00531 |
| Sonnet 5 | $0.00038 | $0.00212 |
| Haiku 4.5 | $0.00019 | $0.00106 |
Grade A, and why
release-summarizer 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.
What it actually says
<load_first> shared/references/changesets.md </load_first>
{
"version": "1.2.0",
"date": "2026-08-04",
"changesets": [
{
"summary": "string (user-facing, carried through from changeset@2 unedited)",
"consumer_impact": "behavior-change|new-capability|internal-only",
"semver_impact": "major|minor|patch|none",
"linked_requirement": "REQ-001",
"commits": ["string"]
}
],
"breaking_changes": ["string"],
"reasoning": "string"
}
reasoning is a scratchpad — include the prior version, which changeset's semver_impact determined the bump, and formatted markdown release notes here. It is not forwarded downstream.
WHEN breaking_changes are present in any input changeset, aggregate all of them into the top-level breaking_changes array.
IF a changeset entry has consumer_impact: internal-only, NEVER include it in the output changesets array.
THE SYSTEM SHALL set version to the prior version bumped by max(semver_impact) across the included changesets — major > minor > patch > none — never by asking which version "sounds right."
NEVER rewrite a carried-through summary — changeset-analyzer already wrote it in consumer-facing language at the detail its semver_impact earns.
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 · 61 lines · 191 tokens per session scan A 969f334443e3
release-summarizer is an agent published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed 5d ago), licensed MIT. It adds 191 tokens to every session and 1,062 once invoked, about $0.0010 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
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
opensource-sanitizer
Verify an open-source fork is fully sanitized before release. Scans for leaked secrets, PII, internal references, and dangerous files using 20+ regex patterns. Generates a PASS/FAIL/PASS-WITH-WARNINGS report. Second stage of the opensource-pipeline skill. Use PROACTIVELY before any public release.
release-captain
Owns the release ritual end-to-end — semver decisions, changelog generation, version bumping, tagging, release notes, deploy gates, rollback rehearsal, and post-release verification. Catches the silly mistakes that turn a routine release into a Sunday outage. Use before cutting any new version, or when a release went…
evolve-changelog-sync
Changelog drift controller (Control archetype) — verifies CHANGELOG/release-notes match shipped commits after every cycle ship.
opensource-sanitizer
Verify an open-source fork is fully sanitized before release. Scans for leaked secrets, PII, internal references, and dangerous files using 20+ regex patterns. Generates a PASS/FAIL/PASS-WITH-WARNINGS report. Second stage of the opensource-pipeline skill. Use PROACTIVELY before any public release.
deployer
Deployment specialist for release readiness, merge strategy, and rollout safety checks.