What is publish-release?

A release-publication step for turning an approved batch of completed work into release notes, a pull request to the main branch, or a tagged release. A pull request is a proposed code change awaiting review and merge.

Use it after an approved merge to publish the batch in the release format defined by the project.

It ensures publication happens only after stakeholder approval and follows the project's versioning and Git rules. If publication is declined, the workflow can continue without releasing it.

publish-release — Skill for OpenCode by nullhack/temple8

Install

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.

Any agent

npx skills add nullhack/temple8 --skill publish-release

Clone the repo

git clone --depth 1 https://github.com/nullhack/temple8

Made for: OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nullhack/temple8/publish-release/github.svg)](https://agentmods.dev/skills/nullhack/temple8/publish-release)

Your own site

<a href="https://agentmods.dev/skills/nullhack/temple8/publish-release"><img src="https://agentmods.dev/badge/skills/nullhack/temple8/publish-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nullhack/temple8/publish-release"><img src="https://agentmods.dev/badge/skills/nullhack/temple8/publish-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 125 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00021	$0.00125
Opus 5.5	$0.00008	$0.00050
Sonnet 5.5	$0.00004	$0.00025
Haiku 4.5	$0.00002	$0.00013

Measured 1mo ago against content hash 051ba1648af8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

publish-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 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.

.opencode/skills/publish-release/SKILL.md · 10 lines

What it actually says

Publish Release

Load [[software-craft/versioning]], [[software-craft/git-conventions]] — release/tag policy and git form.
This step fires only on stakeholder approval (the approved transition from merge); if publication is declined, deliver skips straight to refresh. Publish the batch per the project's release policy: release notes, a PR to main, or a tagged release per [[software-craft/versioning]], [[software-craft/git-conventions]].

Changes

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 · 10 lines · 21 tokens per session scan A 051ba1648af8

Subscribe to this mod's changes

publish-release is a skill published in the GitHub repository nullhack/temple8 (11 stars, last pushed 29d ago), licensed MIT. It adds 21 tokens to every session and 125 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-30.

Git and workflow Productivity Python project-template pytest python-project-template python3 uv

git-push-workflow

This skill should be used when the user says "push", "push to remote", "create PR", "create MR", "pull request", "merge request", "open PR", or when committing and pushing code to GitHub or GitLab. Covers git workflow rules, branch naming conventions, commit message format, and the push + PR/MR creation procedure.

aishajv/claude-everything · 79 tokens

python-release

Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.

ComposioHQ/composio · 53 tokens

repo-guidance

Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK…

ComposioHQ/composio · 67 tokens

publish-release