A release command for publishing a new version of the Tesseract Electron desktop app to GitHub Releases. Electron is a framework for desktop apps built with web technologies.

Use it to check the app repository, update its version, commit the change, create a version tag, and push the release.

It guides the required checks and release steps, reducing the risk of publishing from uncommitted or incorrect app code.

How geckse/markdown-vdb configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to geckse/markdown-vdb. 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/geckse/markdown-vdb/main/.claude/commands/publish-app.md

Clone the repo

git clone --depth 1 https://github.com/geckse/markdown-vdb

Made for: Claude Code.

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/geckse/markdown-vdb/publish-app/github.svg)](https://agentmods.dev/commands/geckse/markdown-vdb/publish-app)

Your own site

<a href="https://agentmods.dev/commands/geckse/markdown-vdb/publish-app"><img src="https://agentmods.dev/badge/commands/geckse/markdown-vdb/publish-app/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/geckse/markdown-vdb/publish-app"><img src="https://agentmods.dev/badge/commands/geckse/markdown-vdb/publish-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 619 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.00000	$0.00619
Opus 5.5	$0.00000	$0.00248
Sonnet 5.5	$0.00000	$0.00124
Haiku 4.5	$0.00000	$0.00062

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

Security

Grade A, and why

publish-app 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 2mo 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.

.claude/commands/publish-app.md · 31 lines

What it actually says

Publish a new version of the Electron desktop app (Tesseract) to GitHub Releases.

The app lives in the app/ git submodule, which is its OWN repository: github.com/geckse/tesseract-md-app. Its release workflow (app/.github/workflows/build-app.yml) triggers on v* tags pushed to THAT repo. Tags in the parent markdown-vdb repo (including the old app-v* scheme) do NOT trigger it.

Steps:

Preflight — the app working tree must be clean:
- git -C app status --porcelain must produce EMPTY output. If it prints anything, ABORT and tell the user to commit or stash their in-progress app work first.
- git -C app branch --show-current must print main (submodules are often in detached-HEAD state; committing there would strand the release commit). If not on main, ABORT and ask the user.
Read the current version from app/package.json and ask the user what the new version should be (suggest patch, minor, major bumps).
Update the version field in app/package.json.
Commit INSIDE the app submodule:
- git -C app add package.json
- git -C app commit -m "chore: bump version to <version>"
Tag v<version> in the app repo and push branch + tag to the app's origin (github.com/geckse/tesseract-md-app):
- git -C app tag v<version>
- git -C app push origin main
- git -C app push origin v<version> That repo's GitHub Actions builds mac (signed + notarized), win (unsigned for beta), and linux, and publishes a DRAFT GitHub release.
Wait for all three matrix jobs to succeed (watch with gh run list -R geckse/tesseract-md-app --workflow build-app.yml), then publish the draft:
- gh release edit v<version> -R geckse/tesseract-md-app --draft=false --generate-notes
In the parent markdown-vdb repo, record the new submodule commit:
- git add app
- git commit -m "chore: bump app submodule to v<version>"
- git push

Notes:

The tag MUST match the v* pattern and MUST be pushed to the APP repo (geckse/tesseract-md-app) to trigger the CI workflow. Do not tag the parent repo.
macOS signing + notarization use the CSC_LINK, CSC_KEY_PASSWORD, APPLE_ID, APPLE_APP_SPECIFIC_PASSWORD, APPLE_TEAM_ID secrets configured in geckse/tesseract-md-app (mac job only). Windows ships unsigned for beta.
Do NOT push without user confirmation

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.

2mo ago First seen · 31 lines · 0 tokens per session scan A 6ce40d1f861f

Subscribe to this mod's changes

publish-app is a command published in the GitHub repository geckse/markdown-vdb (29 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 619 tokens. 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 Releases cli filesystem markdown vector-database

publish-app next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
publish-appgeckse/markdown-vdb	Command	29	2mo ago	MIT	A	0	Claude Code
create-release-note.enfitlab-ai/agent-infra	Command	87	yesterday	MIT	A	8	Claude Code
release.enfitlab-ai/agent-infra	Command	87	yesterday	MIT	A	5	Claude Code
releaseGoldziher/ai-rulez	Command	167	yesterday	MIT	A	4	Claude Code
shipGoldziher/ai-rulez	Command	167	yesterday	MIT	A	4	Claude Code
finish-branch-executeaxiomantic/spellbook	Command	11	2d ago	MIT	A	28	Claude Code
mach12:pr-mergeLeanAndMean/scramjet	Command	8	4d ago	Apache-2.0	A	14	Claude Code

markdown-vdb: Command for Claude Code