Borrowing it
Nothing to install: this file belongs to geleynse/gantry. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/geleynse/gantry/main/.claude/skills/deploy-and-release/SKILL.mdgit clone --depth 1 https://github.com/geleynse/gantryWrote 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/geleynse/gantry/deploy-and-release)<a href="https://agentmods.dev/skills/geleynse/gantry/deploy-and-release"><img src="https://agentmods.dev/badge/skills/geleynse/gantry/deploy-and-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/skills/geleynse/gantry/deploy-and-release"><img src="https://agentmods.dev/badge/skills/geleynse/gantry/deploy-and-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.00052 | $0.02501 |
| Opus 5 | $0.00026 | $0.01251 |
| Sonnet 5 | $0.00010 | $0.00500 |
| Haiku 4.5 | $0.00005 | $0.00250 |
Grade A, and why
deploy-and-release scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
healthcheck: { test: ["CMD", "curl", "-sf", "http://localhost:3100/health"], interval: 30s, timeout: 5s, retries: 3, start_period: 10s } How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy and Release — Gantry
Full walkthroughs (Cloudflare Tunnel, nginx/Caddy configs, systemd unit): docs/deployment.md. This skill covers what's actually wired in CI/CD, the exact scaffolding behavior, and gaps between docs and code. For build mechanics (esbuild config, bun run dev's "stale client bundle" trap, binary packaging internals) see the build-and-dev skill — not duplicated here.
Three deployment shapes
| Shape | Needs on target host | Build step |
|---|---|---|
Docker (docker-compose.yml) |
Docker + Compose only | docker compose up --build (multi-stage Dockerfile builds inside the container) |
| systemd + Bun | Bun runtime | bun install && bun run build (or build:binary) on the host or a build machine |
| Single binary | Nothing — no Bun, no Node, no npm | bun run build:binary on a build machine, then scp the binary |
All three serve one Express process on port 3100 (PORT/GANTRY_PORT), one FLEET_DIR per process, one SQLite file ($FLEET_DIR/data/fleet.db). Only one Gantry instance may run against a given FLEET_DIR — SQLite lock contention otherwise (see docs/getting-started.md "Database locked" troubleshooting entry).
docker-compose.yml (verified against the actual file)
services:
gantry:
build: { context: ., dockerfile: Dockerfile }
image: gantry:local
ports: ["${GANTRY_PORT:-3100}:3100"]
volumes: ["${FLEET_DIR:-./_data}:/data"]
environment:
- FLEET_DIR=/data
- LOG_LEVEL=${LOG_LEVEL:-info}
- TRUST_PROXY=${TRUST_PROXY:-0}
- GANTRY_SECRET=${GANTRY_SECRET:-}
restart: unless-stopped
healthcheck: { test: ["CMD", "curl", "-sf", "http://localhost:3100/health"], interval: 30s, timeout: 5s, retries: 3, start_period: 10s }
Single named volume mount at /data — that's the entire persistence surface: gantry.json, fleet-credentials.enc.json, data/fleet.db, logs/, agent prompt .txt files. Host-side path comes from $FLEET_DIR env var (defaults to ./_data next to the compose file) — this is a host path substituted into the bind mount, separate from the container's FLEET_DIR=/data env var baked into the environment: block. Don't confuse the two when debugging "my config isn't picked up" — the container always reads /data regardless of what the host-side $FLEET_DIR was set to.
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.
- 8d ago First seen · 104 lines · 52 tokens per session scan A dc802707fdda
deploy-and-release is a skill published in the GitHub repository geleynse/gantry (3 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 2,501 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.