ferrogate-release

ferrogate-release is a skill for Claude Code, Codex from lianluo-esign/ferrogate. It costs 88 tokens per session (883 once invoked), scanned A, original, no licence file.

A release guide for FerroGate. It covers building a container image, which packages the application and its dependencies, and publishing it to GHCR, GitHub's container registry.

In plain words
What is it for?
Use it to prepare FerroGate releases, run the required local tests, build musl-static binaries, and publish images with crane.
Why use it?
It defines a local release path that uses the FerroGate end-to-end test suite as a gate instead of GitHub Actions. It also covers hosts without sudo or Docker.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it to prepare FerroGate releases, run the required local tests, build musl-static binaries, and publish images with crane.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lianluo-esign/ferrogate/ferrogate-release
Install

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.

Any agent
npx skills add lianluo-esign/ferrogate --skill ferrogate-release
Clone the repo
git clone --depth 1 https://github.com/lianluo-esign/ferrogate

Made for: Claude Code, Codex.

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.

agentmods badge for ferrogate-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/lianluo-esign/ferrogate/ferrogate-release/github.svg)](https://agentmods.dev/skills/lianluo-esign/ferrogate/ferrogate-release)
Your own site
<a href="https://agentmods.dev/skills/lianluo-esign/ferrogate/ferrogate-release"><img src="https://agentmods.dev/badge/skills/lianluo-esign/ferrogate/ferrogate-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.

agentmods 80×15 button for ferrogate-release

Your own site · 80×15
<a href="https://agentmods.dev/skills/lianluo-esign/ferrogate/ferrogate-release"><img src="https://agentmods.dev/badge/skills/lianluo-esign/ferrogate/ferrogate-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 883 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 unknown 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00088 $0.00883
Opus 5 $0.00044 $0.00441
Sonnet 5 $0.00018 $0.00177
Haiku 4.5 $0.00009 $0.00088

Measured 10d ago against content hash 997bdb066cf3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ferrogate-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.

skills/ferrogate-release/SKILL.md · 73 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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.

  1. 10d ago First seen · 73 lines · 88 tokens per session scan A 997bdb066cf3

Subscribe to this mod's changes

ferrogate-release is a skill published in the GitHub repository lianluo-esign/ferrogate (22 stars, last pushed 5d ago), with no licence file. It adds 88 tokens to every session and 883 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.

Related

Other skills, from other repositories

maintainer-ops

Use for vLLM Semantic Router issue intake, PR decisions, releases, and reviewed GitHub mutations performed on behalf of maintainers.

vllm-project/semantic-router · 32 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens

release

Used to release all toolbox, integrations, agents. Use when releasing a subproject to PyPI, Docker Hub, or when the user asks to release or publish.

memgraph/ai-toolkit · 35 tokens

deployment-operations

Use when planning, executing, diagnosing, verifying, hardening, or rolling back deployments and runtime operations, including releases, Docker Compose, containers, systemd, Kubernetes, health checks, incidents, environment configuration, production or staging troubleshooting, and local development runtime startup.

zhpeng24/devkit · 57 tokens

release-manager

Professional Release Manager Expert skill. Build robust, automated deployment pipelines and configure cloud infrastructure as code.

AtulPurohit/Antigravity-Awesome-Skills · 22 tokens

release-and-publish

Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…

cyanheads/brapi-mcp-server · 112 tokens