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 skills add dynos-fit/dynos-work --skill release-executorgit 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/skills/dynos-fit/dynos-work/release-executor)<a href="https://agentmods.dev/skills/dynos-fit/dynos-work/release-executor"><img src="https://agentmods.dev/badge/skills/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/skills/dynos-fit/dynos-work/release-executor"><img src="https://agentmods.dev/badge/skills/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.00035 | $0.00167 |
| Opus 5.5 | $0.00014 | $0.00067 |
| Sonnet 5.5 | $0.00007 | $0.00033 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
execution/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 1mo 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: execution/release-executor
Spawn the release-executor agent with the user's prompt as the instruction.
Ruthlessness Standard
- Do not let release metadata drift across package/plugin manifests.
- Rollout and rollback behavior must be concrete enough for an operator to follow.
- Migration and compatibility windows must be explicit when state or contracts change.
What to pass
Pass the user's full prompt verbatim. Do not summarize or sanitize it. Prepend a short hard wrapper that tells the agent to keep release artifacts consistent, verify changelog/version hygiene, and document rollback-sensitive behavior before writing 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.
- 1mo ago First seen · 21 lines · 35 tokens per session scan A 2384141ee32a
execution/release-executor is a skill published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 167 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 skills, from other repositories
release-docs
Diff-driven documentation sync after a release. Determines what source files changed, delegates changelog to zuvo:docs, updates only docs whose source changed. Flags: --dry-run, explicit range argument.
ship
/ship - Release Pipeline Commander.
release
Use this agent for versioning, changelogs, release notes, deployment coordination, and release process management.
changelog
Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.
ds-ship
Ship orchestrator — classify the project, pick a mode (improve/release/launch/maintain), delegate only the skills the project's signals justify, consolidate findings, produce an audit report. Use for an end-to-end audit or ship pipeline across multiple skills.
ds-freeze
Release scope triage — decide which features ship this release vs defer to backlog, then file/implement the kept set and sync docs to match. Use when a release has grown too complex to finish or polish everything and the team needs to cut scope deliberately.