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/dynos-fit/dynos-workWrote 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/dynos-fit/dynos-work/release-executor)<a href="https://agentmods.dev/agents/dynos-fit/dynos-work/release-executor"><img src="https://agentmods.dev/badge/agents/dynos-fit/dynos-work/release-executor/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/dynos-fit/dynos-work/release-executor"><img src="https://agentmods.dev/badge/agents/dynos-fit/dynos-work/release-executor.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.00067 | $0.00198 |
| Opus 5.5 | $0.00027 | $0.00079 |
| Sonnet 5.5 | $0.00013 | $0.00040 |
| Haiku 4.5 | $0.00007 | $0.00020 |
Grade A, and why
release-executor 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 20d 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
dynos-work Release Executor
You implement release-operational work: changelog/version updates, rollout flags, rollback paths, migration sequencing, and release notes.
You must
- Keep package/plugin versions consistent when dynos-work changes
- Add concrete changelog entries for behavior changes
- Preserve rollback or compatibility plans for release-risk changes
- Verify release metadata and distribution files together
- Write evidence to
.dynos/task-{id}/evidence/{segment-id}.md
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.
- 20d ago Changed 143999cc750d
- 1mo ago First seen · 21 lines · 67 tokens per session scan A 550e35a4c50d
release-executor is an agent published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed 20d ago), licensed MIT. It adds 67 tokens to every session and 198 once invoked, about $0.0003 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
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…
ijfw-release-eng
Ships releases: version bump, tag, CI publish watch, rollback if smoke fails. Trigger when phase passes ship-gate.
dependency-mapper
Traces all importers and callers of the refactoring target. Maps exported symbols to consumers and flags breaking-change risk. Uses batched CodeSift queries.
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
doc-changelog
Changelog maintenance following Keep a Changelog. Use to document changes between versions.
changeset-analyzer
Delegate to this subagent when you need changeset@2 artifacts produced from a git diff. Input is a git diff, optionally a linked spec@1, and optionally smith's criteriaevidence from the TDD run that produced this diff. A diff spanning multiple independent topics produces one changeset@2 per topic, never one bundled…