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 lianluo-esign/ferrogate --skill ferrogate-releasegit clone --depth 1 https://github.com/lianluo-esign/ferrogateWrote 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/lianluo-esign/ferrogate/ferrogate-release)<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.
<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>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.00088 | $0.00883 |
| Opus 5.5 | $0.00035 | $0.00353 |
| Sonnet 5.5 | $0.00018 | $0.00177 |
| Haiku 4.5 | $0.00009 | $0.00088 |
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 1mo 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.
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.
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.
- 1mo ago First seen · 73 lines · 88 tokens per session scan A 997bdb066cf3
ferrogate-release is a skill published in the GitHub repository lianluo-esign/ferrogate (29 stars, last pushed 1mo ago), with no licence file. It adds 88 tokens to every session and 883 once invoked, about $0.0004 per session on Opus 5.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
validate-release-green
Run or inspect the local Release-Green observer for an exact base or combined PR candidate, separating hard failures, advisory drift and incomplete evidence. Use for maintainer preflight; full CI acceptance remains a separate requirement.
maintainer-ops
Use for vLLM Semantic Router issue intake, PR decisions, releases, and reviewed GitHub mutations performed on behalf of maintainers.
deploy-akashic
A deployment procedure for an Akashic project that checks and merges an approved pull request, then submits the resulting code revision to update a Docker-based service. The host system handles stopping, moving, and restarting the service.
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.
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.
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, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…