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 skills add olgaiv39/claude-oss-skills --skill release-deploygit clone --depth 1 https://github.com/olgaiv39/claude-oss-skillsWrote 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/olgaiv39/claude-oss-skills/release-deploy)<a href="https://agentmods.dev/skills/olgaiv39/claude-oss-skills/release-deploy"><img src="https://agentmods.dev/badge/skills/olgaiv39/claude-oss-skills/release-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.
<a href="https://agentmods.dev/skills/olgaiv39/claude-oss-skills/release-deploy"><img src="https://agentmods.dev/badge/skills/olgaiv39/claude-oss-skills/release-deploy.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.00075 | $0.01439 |
| Opus 5 | $0.00037 | $0.00720 |
| Sonnet 5 | $0.00015 | $0.00288 |
| Haiku 4.5 | $0.00007 | $0.00144 |
Grade A, and why
release-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 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-deploy
Prepare a project for release, then deploy it to the target the project actually uses. Run the pre-release checks first. Never commit, tag, push, publish, or deploy without explicit user intent for that specific action.
Activate when
- The project is at a release or submission boundary
- A verified build needs to be shipped to a deployment target
- A package needs to be published to a registry
Do not activate when
- Code is still being written or fixed -> use
implement-minimalortest-and-debug - The change only needs a review, not a release -> use
public-code-review - The repository does not exist yet -> use
oss-bootstrap
Required inputs
- Confirmation that this is a release boundary
- The intended deployment target, if known
- Explicit intent for any commit, tag, push, publish, or deploy action
Low-resource policy
Read the first of these that exists, then follow it. Full validation runs only at this boundary:
${CLAUDE_PROJECT_DIR}/.claude/shared/LOW_RESOURCE.md$HOME/.claude/shared/LOW_RESOURCE.md
If neither exists, apply this fallback: run one expensive command at a time, prefer the narrowest validation first, disable watch mode, reuse existing environments, and run full validation only at this milestone. Do not scan the whole filesystem to locate the policy.
Context-efficiency policy
Read the first of these that exists, then follow it:
${CLAUDE_PROJECT_DIR}/.claude/shared/CONTEXT_EFFICIENCY.md$HOME/.claude/shared/CONTEXT_EFFICIENCY.md
If neither exists, apply this fallback: select files before reading; use targeted searches and bounded ranges; do not preload references; do not reread unchanged files; finish one atomic increment and stop; create a compact handoff before context is exhausted.
Facts that must not be assumed
- The deployment target; detect it, do not guess
- The build, test, and publish commands
- That credentials for a target are present and valid
- That the user wants any push, publish, or deploy performed now
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/archestra-app.md 1.5 KB
- references/docker.md 1.5 KB
- references/github-repository.md 1.4 KB
- references/mcp-server.md 1.6 KB
- references/node-service.md 1.4 KB
- references/package-release.md 1.7 KB
- references/python-service.md 1.4 KB
- references/static-and-pages.md 1.5 KB
- references/target-detection.md 1.9 KB
- templates/deployment-checklist.md 1.1 KB
- templates/release-report.md 972 B
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 · 172 lines · 75 tokens per session scan A 9013f6dd45dd
release-deploy is a skill published in the GitHub repository olgaiv39/claude-oss-skills (12 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 1,439 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
agentplane-release-and-packaging-operator
Use when preparing, validating, publishing, auditing, or recovering an Agentplane release, especially package build ordering, version parity, npm/GitHub/GHCR/external distribution publication, public install smoke tests, hosted publish evidence, or release CI failures.
checking-release-readiness
Records a ship, block, defer, or ship-with-risk decision that ties baseline, evidence status, residual risk, rollback, monitoring, and handoff together. Use when a packet, PR, release, dependency change, or agent-authority change approaches merge. Do not use early in development before evidence exists.
brpr
(devtools plugin) Create a branch, commit changes, push, and open a PR — or just commit+push+PR if already on a feature branch. Links related issues from GitHub or Linear based on project tracker config.
release
Automate the release process. Use when user says "cut a release", "new version", "bump version", "publish release", or anything about versioning and publishing.
ship
Use when code is ready to ship — creates PRs, merges, deploys, and verifies. Handles the full PR-to-production pipeline. Triggers on /ship.
ship
Use when work should go live — commit, push, deploy per recipe, cache-busted live verify, smoke, screenshot. Blocks the "shipped" claim on the live check.