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 skills/aaronnat23/disp8ch/release-managernpx skills add aaronnat23/disp8ch --skill release-managergit clone --depth 1 https://github.com/aaronnat23/disp8chWrote 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/skills/aaronnat23/disp8ch/release-manager)<a href="https://agentmods.dev/skills/aaronnat23/disp8ch/release-manager"><img src="https://agentmods.dev/badge/skills/aaronnat23/disp8ch/release-manager.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.00000 | $0.00054 |
| Opus 5 | $0.00000 | $0.00027 |
| Sonnet 5 | $0.00000 | $0.00011 |
| Haiku 4.5 | $0.00000 | $0.00005 |
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 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.
What it actually says
Release Manager
Use workflows, boards, hierarchy, and council together when coordinating a release or rollout.
- Keep launch work tied to goals and owners.
- Surface blockers, approvals, and rollback checks early.
- Prefer a short go/no-go recommendation backed by evidence.
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 · 8 lines · 0 tokens per session scan A a0bb8d996c02
release-manager is a skill published in the GitHub repository aaronnat23/disp8ch (98 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 54 tokens. 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 skills, from other repositories
release
Prepare and publish stable Agent Lightning releases through the repository's version bump, pull-request checks, merge, tag, PyPI trusted-publishing, and versioned-documentation workflows. Use when asked to plan, cut, verify, or explain a release; treat nightly TestPyPI builds as a separate path.
ship-feature
Ship a feature end-to-end — update tests, docs, docs-site, then release to PyPI. Use when user says "ship", "ship feature", "release", or asks to publish a new version.
git-changelog
Use this skill when the task involves generating a changelog, release notes, or commit summary from a Git repository's history. Suitable for tasks like "generate a changelog for v2.0", "summarize what changed since last release", or "create release notes from git commits". Requires access to a Git repository.
release-notes
Maintain Mozaiks release notes proactively. Use when changing released behavior, preparing a PyPI/GitHub release, bumping versions, modifying generated app scaffolds, changing public install/setup docs, or reviewing whether a change needs a changelog entry.
synthetic-release-notes
Draft release notes from user-provided changes.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.