Higress is a cloud-native API gateway built on Istio and Envoy that routes and manages APIs and can be extended with WebAssembly plugins. It is used to manage APIs for AI models and MCP servers as well as general services, and the catalogue entries provide agent workflows and integrations for operating it.
Borrowing it
Nothing to install: this file belongs to higress-group/higress. 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/higress-group/higress/main/.agents/skills/higress-update-envoy-gateway/SKILL.mdgit clone --depth 1 https://github.com/higress-group/higressWrote 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/higress-group/higress/higress-update-envoy-gateway)<a href="https://agentmods.dev/skills/higress-group/higress/higress-update-envoy-gateway"><img src="https://agentmods.dev/badge/skills/higress-group/higress/higress-update-envoy-gateway/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/higress-group/higress/higress-update-envoy-gateway"><img src="https://agentmods.dev/badge/skills/higress-group/higress/higress-update-envoy-gateway.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 80 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00119 | $0.01207 |
| Opus 5 | $0.00060 | $0.00603 |
| Sonnet 5 | $0.00024 | $0.00241 |
| Haiku 4.5 | $0.00012 | $0.00121 |
Grade A, and why
higress-update-envoy-gateway 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 12d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Higress Envoy Gateway Dependency Update
Core Workflow
Run from the Higress repo root unless a step explicitly says otherwise.
-
Verify context:
- Check
git status --short --branch. - Do not remove unrelated user changes or generated artifacts.
- Use
ghfor GitHub release/PR checks and always pass--repofor non-current repos.
- Check
-
Build Envoy packages from the current branch:
git submodule update --init make build-envoyExpected artifacts land in
external/package/, typically:envoy-alpha-<proxy-sha>.tar.gzenvoy-symbol-<proxy-sha>.tar.gz- matching
.sha256and.dwpfiles
-
Publish Envoy package release in
higress-group/proxy:- Create a new release tag by incrementing the requested RC/test tag, for example
v2.2.4-rc.2-test-cpp-host. - Match the reference release asset names, even if local filenames include SHAs:
- local
envoy-alpha-<sha>.tar.gzuploads asenvoy-amd64.tar.gz - local
envoy-symbol-<sha>.tar.gzuploads asenvoy-symbol-amd64.tar.gz
- local
- Use temporary renamed copies rather than renaming source artifacts:
cp external/package/envoy-alpha-<sha>.tar.gz /tmp/envoy-amd64.tar.gz cp external/package/envoy-symbol-<sha>.tar.gz /tmp/envoy-symbol-amd64.tar.gz gh release create <release-tag> /tmp/envoy-amd64.tar.gz /tmp/envoy-symbol-amd64.tar.gz \ --repo higress-group/proxy --target <target-branch> --title <release-tag> --generate-notes gh release view <release-tag> --repo higress-group/proxy --json tagName,targetCommitish,assets,url - If following an existing reference release, inspect it first with
gh release view.
- Create a new release tag by incrementing the requested RC/test tag, for example
-
Update Higress Makefile dependencies:
- In
Makefile.core.mk, set:export ENVOY_PACKAGE_URL_PATTERN?=https://github.com/higress-group/proxy/releases/download/<release-tag>/envoy-symbol-ARCH.tar.gz - After building and pushing the gateway image, set:
ENVOY_LATEST_IMAGE_TAG ?= <gateway-image-tag>
- In
What ships with it
1 file 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.
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.
- 12d ago First seen · 95 lines · 119 tokens per session scan A 57bdf65bf976
higress-update-envoy-gateway is a skill published in the GitHub repository higress-group/higress (9,365 stars, last pushed yesterday), licensed Apache-2.0. It adds 119 tokens to every session and 1,207 once invoked, about $0.0006 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-31.
Other skills, from other repositories
verify
Build the computer-use-demo image and drive the Streamlit UI headlessly to verify changes end-to-end.
zero-script-qa
Zero Script QA — test without scripts using structured JSON logging and Docker monitoring. Triggers: zero-script-qa, log testing, docker logs, QA.
local-test
Build, run, and test IronClaw locally using Docker containers and Chrome MCP browser automation.
wiremock-standalone-docker
Provides patterns and configurations for running WireMock as a standalone Docker container. Generates mock HTTP endpoints, creates stub mappings for testing, validates integration scenarios, and simulates error conditions. Use when you need to mock APIs, create a mock server, stub external services, simulate…
API Gateway Testing
API gateway testing skill covering rate limiting validation, request routing, authentication proxy testing, load balancing verification, circuit breaker testing, and gateway configuration validation for Kong, Envoy, and AWS API Gateway.
branchbox-devcontainer-guardrails
Use when modifying BranchBox devcontainer/bootstrap workflows, compose templates, feature env-stash behavior, or manual E2E harness/release docs. Apply issue.