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/thiientv/godmode/release-engineeringnpx skills add thiientv/godmode --skill release-engineeringgit clone --depth 1 https://github.com/thiientv/godmodeWhat 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.00076 | $0.00541 |
| Opus 5 | $0.00038 | $0.00270 |
| Sonnet 5 | $0.00015 | $0.00108 |
| Haiku 4.5 | $0.00008 | $0.00054 |
Grade A, and why
release-engineering 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Engineering
Turn a release into a sequence of evidence-backed decisions rather than one irreversible event.
Build the release contract
Record the artifact/version, environments, owner, change scope, affected users, data or contract changes, dependencies, risk class, maintenance window, and success metrics. Use release-record.md for the go/no-go and rollout record.
Establish gates
Require checks proportional to risk: build and tests, contract and migration proof, security findings, performance budgets, smoke paths, accessibility or visual checks, artifact signing/provenance, monitoring, and a tested recovery path. A green generic pipeline is not proof of the release's critical behavior.
Roll out safely
- Separate deployment from exposure with a flag or routing control when practical.
- Start with internal, shadow, canary, or low-percentage traffic.
- Compare errors, latency, saturation, business outcomes, and support signals against a pre-release baseline.
- Promote only after the observation window and all gates pass.
- Roll back or disable immediately when a predefined threshold is crossed.
- Verify recovery, communicate status, and preserve the timeline.
For canaries and production observation windows, use
post-deploy-verification.md. Confirm
the deployed build marker, run critical browser journeys through
browser-testing, and record each promote, hold, or rollback decision against
fresh baseline evidence.
Use immutable artifacts across environments. Keep release credentials out of logs and command lines. Require explicit authority for production mutation.
Close the release
Verify critical paths after deployment, monitor delayed jobs and regional
effects, remove stale flags and compatibility paths on schedule, update release
notes, and create owned follow-ups for non-blocking debt. Never substitute a
successful deployment command for an observation window. Use
incident-response if live impact begins and safe-migrations for stateful
cutovers.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 65 lines · 76 tokens per session scan A 5b42eac0fb9e
release-engineering is a skill published in the GitHub repository thiientv/godmode (93 stars, last pushed 7d ago), licensed MIT. It adds 76 tokens to every session and 541 once invoked, about $0.0004 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-30.
Other skills, from other repositories
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
repo-recap
Generate a comprehensive repo recap (PRs, issues, releases) for sharing with team. Pass "en" or "fr" as argument for language (default fr).
release-jetbrains
Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
om-auto-update-changelog
Open Mercato releases must keep CHANGELOG.md, UPGRADENOTES.md, and version-specific downstream migration skills aligned. Apply this contract after the external skill resolves {version}, {date}, and the previous changelog release, but before it edits files or delegates to om-auto-create-pr.
document-release
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/AGENTS.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs".…