Borrowing it
Nothing to install: this file belongs to nerds-odd-e/doughnut. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nerds-odd-e/doughnut/main/.agents/skills/release-application/SKILL.mdgit clone --depth 1 https://github.com/nerds-odd-e/doughnutWrote 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/nerds-odd-e/doughnut/release-application)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/release-application"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/release-application/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/nerds-odd-e/doughnut/release-application"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/release-application.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.00036 | $0.00684 |
| Opus 5.5 | $0.00014 | $0.00274 |
| Sonnet 5.5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
release-application 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Application
Use the application release runbook as the canonical procedure and evidence contract. Read it before acting; keep command details and recovery mechanics there rather than reconstructing them in this skill.
Route the request
- An application release publishes the SPA, bundled CLI, routing, and any
required backend rollout through the Application Release workflow. A
cli-*release and PR delivery are independent. - A status-only request is read-only. Inspect existing tags, workflow runs, publication jobs, and smoke evidence without creating a tag or rerunning a workflow.
- Preserve authorization already provided by the user. Do not ask again when the exact release identity and authorization are already clear. Before an immutable tag push, resolve any genuinely missing intended version, commit identity, or authority to publish.
Release and verify
For a requested release, establish the intended unused, increasing stable
version and the exact release commit on main. Confirm successful applicable CI
and the required artifacts: exact-commit CI takes precedence; without it, the
runbook permits the nearest first-parent ancestor with CI evidence only while
tree differences match the tagged revision's workflow ignore policy. Pending or
failed evidence must not be bypassed for an older green run. A documentation-only
tag can reuse that build without starting CI. Push the immutable tag only when
authorized. CI completion does not start Application Release; if a tag was pushed
prematurely, an explicit release workflow rerun is needed after CI succeeds.
Follow the runbook for the commands and admission rules.
After the release request is admitted, inspect the selected tag, release SHA,
build SHA (ciSha), CI run
and attempt, the actual publication job, and the production smoke-check
evidence. Do not infer deployment from a tag, CI success, admission, or an
overall workflow result alone. waiting, blocked, failed, or skipped
publication is not deployed.
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 Changed · +10 lines 6b4b452e09ce
- 1mo ago Changed · -1 lines · -4 tokens per session bf0ea3a5f7ee
- 1mo ago First seen · 59 lines · 40 tokens per session scan A 67aa10aac16f
release-application is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 684 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-09-07.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
xberg-release
Xberg release on top of the shared release-workflow: mise run version:sync to bindings and chart, CI/Publish/Benchmarks readiness. Use before a release.
factory-ship
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…