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.
npx agentmods add skills/laurigates/claude-plugins/deploy-releasenpx skills add laurigates/claude-plugins --skill deploy-releasegit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/deploy-release)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/deploy-release"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/deploy-release.svg" alt="Measured on agentmods" 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.00035 | $0.01533 |
| Opus 5 | $0.00017 | $0.00766 |
| Sonnet 5 | $0.00007 | $0.00307 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
deploy-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 2d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Creation Command
Create GitHub releases using release-please automation or manual release workflows for containerized applications.
When to Use This Skill
| Use this skill when... | Use deploy-handoff instead when... |
|---|---|
Cutting a new release from main and tagging a version |
Documenting an already-deployed service for another developer or client |
| Setting up or auditing release-please automation and manifests | Generating access URLs, monitoring links, and onboarding checklists for a deployed resource |
| Publishing a manual GitHub release, draft, or pre-release | Producing handoff prose for a ticket rather than cutting a version |
| Driving the version-tag side of a containerized release pipeline | Building or hardening container images themselves (use container-development) |
Context
- Git remotes: !
git remote -v - Branch: !
git branch --show-current - Recent tags: !
git tag --sort=-v:refname -l 'v*' --format='%(refname:short)' -n5 - Last release commit: !
git log --oneline --max-count=5 - Release config: !
find . -maxdepth 1 -name 'release-please-config.json' - Manifest: !
find . -maxdepth 1 -name '.release-please-manifest.json' - Changelog: !
find . -maxdepth 1 -name 'CHANGELOG.md'
Parameters
Parse from $ARGUMENTS:
$1(VERSION): Semantic version string (e.g.,1.2.0,v2.0.0-rc.1)--draft: Create release as draft (not published)--prerelease: Mark as pre-release
Execution
Execute this release workflow:
Step 1: Determine release strategy
Check whether the project uses release-please or manual releases:
- If
release-please-config.jsonexists, use the release-please workflow - If no release-please config exists, use the manual release workflow
Step 2a: Release-please workflow
If release-please is configured:
- Verify conventional commits exist since last release tag
- Check for an open release PR:
gh pr list --label "autorelease: pending" --json number,title,url - If a release PR exists, report its status and URL
- If no release PR exists, explain that release-please creates PRs automatically from conventional commits
- Provide guidance on merging the release PR to trigger the release
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.
- 2d ago First seen · 171 lines · 35 tokens per session scan A 2fc19adffabd
deploy-release is a skill published in the GitHub repository laurigates/claude-plugins (58 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,533 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-09-03.
Other skills, from other repositories
changelog-summarizing
Use this skill when the user asks to summarize, recap, or post about repository changes in the Shopware AI Coding Tools marketplace since a given date — phrases like "write a changelog post for Discord", "recap this week's commits for Slack", "summarize what shipped since 2026-04-01", "draft a release announcement".…
plugin-updating
Use this skill when the user asks to bump, update, or release a new version of a plugin in the Shopware AI Coding Tools marketplace — phrases like "bump test-writing to 3.8.0", "release a patch for dev-tooling", "update the plugin version". Handles synchronized version bumps across plugin.json and every SKILL.md…
changelog
Ingest Claude Code changelog entries and integrate them into the current repo. Fetch (read-only display), diff (impact analysis, no edits), status (applied versions), and apply (full integrate pipeline, explicit user intent only). Use when: 'new cc version', 'what changed in claude code', 'apply changelog', a new CC…
release-info-writing
Use this skill when the user is completing features, deprecations, or breaking changes in the Shopware core repository that affect external developers, or when they ask to write release info, upgrade entries, release notes, release documentation, or changelog entries — phrases like "write a release info entry for my…
a0-contribute-plugin
Guide for publishing an Agent Zero plugin to the community Plugin Index (a0-plugins repo). Covers GitHub repo setup, index.yaml creation, CI validation rules, and PR submission. Use when the user wants to share, publish, submit, or contribute a plugin to the Plugin Hub so other Agent Zero users can find and install it.
quick-pr
Split a minor change from the current work into a separate worktree and open a PR without interrupting your flow. Use when an unrelated small fix (typo, lint rule, config tweak) is sitting in a feature branch and the user wants it shipped on its own — "quick PR", "split this out", "ship this separately". Requires…