A command that runs the complete release procedure for Shiki, including version changes, changelog updates, documentation checks, publishing, and store or website updates.

Use it to cut a specified Shiki version, or the next patch version when no version is supplied, from a clean Git branch.

It provides one ordered runbook for the many steps in a release, with checks intended to catch an incomplete or inconsistent publication.

How sazardev/shiki configures OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to sazardev/shiki. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/sazardev/shiki/main/.opencode/command/deploy.md

Clone the repo

git clone --depth 1 https://github.com/sazardev/shiki

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/commands/sazardev/shiki/deploy/github.svg)](https://agentmods.dev/commands/sazardev/shiki/deploy)

Your own site

<a href="https://agentmods.dev/commands/sazardev/shiki/deploy"><img src="https://agentmods.dev/badge/commands/sazardev/shiki/deploy/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/commands/sazardev/shiki/deploy"><img src="https://agentmods.dev/badge/commands/sazardev/shiki/deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 781 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.00041	$0.00781
Opus 5.5	$0.00016	$0.00312
Sonnet 5.5	$0.00008	$0.00156
Haiku 4.5	$0.00004	$0.00078

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

Security

Grade A, and why

deploy 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/command/deploy.md · 43 lines

What it actually says

Execute the full shiki release process by loading the deploy skill and following its runbook exactly (use the skill tool with name deploy — it lives at .opencode/skill/deploy/SKILL.md and is the verified, step-by-step procedure). This command is the entry point that drives it.

Version to cut: $1 (e.g. 0.9.2). If omitted, derive it from the current [workspace.package] version in the root Cargo.toml (default = next patch).

Work through the runbook in order, checking off each phase:

Preflight — clean tree on main, synced; enumerate git log --oneline <last-tag>..main.
CHANGELOG — audit [Unreleased] against those commits (run the docs-coherence skill first if unsure what's missing); rename to [<version>] - <date> and re-add an empty [Unreleased].
Version bump — [workspace.package] + the three [workspace.dependencies] shiki-* in root Cargo.toml; docs/index.html JSON-LD softwareVersion.
Docs site + config prose — fix anything the coherence audit flagged; keep the built-in /-menu command lists in sync across docs/documentation.html, IDEA.md, and shiki-config/src/config.rs (section_comment).
Image/video scripts — if this release has visual headline features, add a shot to scripts/screenshots.sh and a Phase to scripts/demo-gif.sh (new sample notes go in research/, never personal/); bash -n both.
Verify + commit + push — cargo check/clippy -D warnings/test/fmt all green, then commit with [PUBLISH] in the message (chore: cut release for vX.Y.Z [PUBLISH]) and push to main.
Ensure release.yml runs — if no Release run appears within ~1–2 min of auto-tag finishing, dispatch it manually: gh workflow run release.yml --ref main --field tag=vX.Y.Z.
Monitor release.yml — builds → GitHub Release → crates.io → packaging manifests. If update-packaging-manifests fails at "Push Homebrew tap" (403 on sazardev/homebrew-shiki), push the formula manually from the tap clone.
Skipped jobs — if update-screenshots/update-release-pages were skipped, run scripts/screenshots.sh, scripts/demo-gif.sh, and scripts/generate_release_pages.py --version X.Y.Z locally, copy into docs/, commit, push.
Verify every store — GitHub Release assets + checksums, crates.io ×4, AUR shiki-bin + shiki, Homebrew tap, Scoop (byte-identical manifests), and the live site (softwareVersion, changelog page, OG card, feed). Report a store-by-store table to the user, noting any manual fallback that was needed.

Never git tag/push tags by hand (auto-tag does it). Never finish without the store-by-store verification and a clean working tree.

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 · 43 lines · 41 tokens per session scan A 77863d850175

Subscribe to this mod's changes

deploy is a command published in the GitHub repository sazardev/shiki (335 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 781 once invoked, about $0.0002 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-10.

CI and CD DevOps and cloud Git and workflow Productivity Releases cli markdown note-taking notes

deploy next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
deploysazardev/shiki	Command	335	yesterday	MIT	A	41	OpenCode
audit-releasestarter-series/create-starter	Command	2	2d ago	MIT	A	39	Claude Code
post-release.enfitlab-ai/agent-infra	Command	87	yesterday	MIT	A	4	Claude Code
ciGenerous-Corp/pulp	Command	22	today	MIT	A	14	Claude Code
releaseGoldziher/ai-rulez	Command	167	yesterday	MIT	A	4	Claude Code
deployNickRomanek/clawbridge	Command	23	19d ago	Apache-2.0	A	0	Claude Code
create-prdsswift/ion	Command	5	yesterday	MIT	A	28	Claude Code

shiki: Command for OpenCode