Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/synaptiai/synapti-marketplacenpx agentmods add commands/synaptiai/synapti-marketplace/gh-releaseWrote 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/commands/synaptiai/synapti-marketplace/gh-release)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/gh-release"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-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/commands/synaptiai/synapti-marketplace/gh-release"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-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.00000 | $0.02454 |
| Opus 5 | $0.00000 | $0.01227 |
| Sonnet 5 | $0.00000 | $0.00491 |
| Haiku 4.5 | $0.00000 | $0.00245 |
Grade A, and why
gh-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 10d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Release v$ARGUMENTS
Create a new release for the marketplace or a specific plugin.
Tool Usage: This workflow uses the AskUserQuestion tool extensively to determine release type, target, and get explicit approval before creating irreversible releases.
Arguments
$ARGUMENTS: Version bump type -patch,minor, ormajorpatch(1.2.0 → 1.2.1): Bug fixes onlyminor(1.2.0 → 1.3.0): New featuresmajor(1.2.0 → 2.0.0): Breaking changes
If no argument provided, analyze commits to suggest the appropriate bump type.
Phase 1: Preparation
-
Ensure on latest main:
git checkout main && git pull origin main -
Check what's changed since last release:
git log $(git describe --tags --abbrev=0)..HEAD --oneline -
Get current versions:
# Marketplace version cat .claude-plugin/marketplace.json | grep '"version"' # Plugin versions cat plugins/*/.claude-plugin/plugin.json | grep '"version"' -
If no argument provided, use the AskUserQuestion tool to determine release type:
Analyze commits and present recommendation:
- Option 1: "patch (X.Y.Z → X.Y.Z+1)" - Bug fixes only (Recommended if all fix: commits)
- Option 2: "minor (X.Y.Z → X.Y+1.0)" - New features (Recommended if feat: commits)
- Option 3: "major (X.Y.Z → X+1.0.0)" - Breaking changes
-
Use the AskUserQuestion tool to determine release target:
- Option 1: "Marketplace only" - Bump marketplace.json version
- Option 2: "Plugin: [name]" - Bump plugin.json AND marketplace.json entry
- Option 3: "Both" - Changes span marketplace and plugin
Phase 1.5: Impact Assessment & Approval
Before making any changes, present a complete impact assessment, then use the AskUserQuestion tool to get explicit approval:
First, display the assessment:
**Release Impact Assessment**
Release type: [patch/minor/major]
Target: [Marketplace / Plugin: {name} / Both]
**Current versions:**
- Marketplace: X.Y.Z
- Plugin ({name}): X.Y.Z
**Proposed changes:**
- [ ] plugins/{name}/.claude-plugin/plugin.json: X.Y.Z → X.Y.Z+1
- [ ] .claude-plugin/marketplace.json plugins[].version: X.Y.Z → X.Y.Z+1
- [ ] .claude-plugin/marketplace.json metadata.version: X.Y.Z → X.Y.Z+1 (if marketplace release)
**Commits included in this release:**
- abc1234 feat: add new analysis capability
- def5678 fix: correct link in documentation
- ghi9012 docs: update README
**Breaking changes:** None / [list if any]
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.
- 10d ago First seen · 318 lines · 0 tokens per session scan A 5b690d338a66
gh-release is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,454 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-31.
Other commands, from other repositories
create-worktree
Follow these steps to create a git worktree.
ship
Ship workflow — detect base branch, merge, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
document-release
Post-ship documentation update — reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped.
deploy
Start Phase 6 — propose a deployment for human approval and, once approved, execute with post-deploy verification.
release-update
(dev-only) release-update maintainer harness — Claude Code upstream change tracker (release-notes version-delta sweep + docs sync). NOT distributed to user projects.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.