Borrowing it
Nothing to install: this file belongs to SlideSpeak/slidespeak-onbrand. 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/SlideSpeak/slidespeak-onbrand/develop/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/SlideSpeak/slidespeak-onbrandWrote 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/slidespeak/slidespeak-onbrand/release)<a href="https://agentmods.dev/skills/slidespeak/slidespeak-onbrand/release"><img src="https://agentmods.dev/badge/skills/slidespeak/slidespeak-onbrand/release/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/slidespeak/slidespeak-onbrand/release"><img src="https://agentmods.dev/badge/skills/slidespeak/slidespeak-onbrand/release.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.00039 | $0.01057 |
| Opus 5 | $0.00019 | $0.00528 |
| Sonnet 5 | $0.00008 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
release 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 9d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Run the full release path for this repository:
- Find and merge the Release Please PR into
develop. - Open or update the promotion PR from
developtomain. - Merge the promotion PR into
mainwith a merge commit.
Do the whole release. Do not stop after opening PRs unless the user explicitly asks for a pause or a required approval is missing.
Preconditions
- Work from a clean tree. If local changes exist, inspect them and avoid overwriting user work.
- Use
ghfor GitHub operations andgitfor local branch state. - Treat CI status as authoritative. Before merging each PR, verify all required checks are passing.
- If a check fails, investigate, fix the repository, push the fix, and wait for CI again.
- Preserve release history:
- Release Please PR into
develop: squash merge. - Promotion PR from
developtomain: merge commit.
- Release Please PR into
Find the Release Please PR
Look for an open PR created by the Release Please bot against develop. It is usually titled like
chore: release ..., chore(...): release ..., or similar.
gh pr list \
--state open \
--base develop \
--json number,title,author,headRefName,baseRefName,url,labels,statusCheckRollup,mergeStateStatus \
--jq '.[] | select((.author.login | test("release-please|github-actions|app/release-please"; "i")) or (.title | test("^chore(\\(.+\\))?: release"; "i")) or ([.labels[].name] | index("release-please")))'
If multiple candidates exist, inspect each one and pick the active Release Please PR that updates version files, changelogs, or release manifests. If none exists, report that there is no pending release PR and stop.
Verify and Fix CI
For each PR before merging:
gh pr view {number-or-url} --json number,title,url,headRefName,baseRefName,mergeStateStatus,statusCheckRollup
gh pr checks {number-or-url} --watch
If checks are failing:
- Read failing logs with
gh run view/gh run watch/gh run downloadas needed. - Reproduce locally where practical with the matching package script from
package.json. - Fix the actual issue in the repo, commit or amend on the relevant PR branch, push, and wait for CI again.
- Do not merge with failing or pending required checks.
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.
- 9d ago First seen · 128 lines · 39 tokens per session scan A efdd723fd62d
release is a skill published in the GitHub repository SlideSpeak/slidespeak-onbrand (7 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 1,057 once invoked, about $0.0002 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-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.