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/nginx-to-higress-migration/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/nginx-to-higress-migration)<a href="https://agentmods.dev/skills/higress-group/higress/nginx-to-higress-migration"><img src="https://agentmods.dev/badge/skills/higress-group/higress/nginx-to-higress-migration/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/nginx-to-higress-migration"><img src="https://agentmods.dev/badge/skills/higress-group/higress/nginx-to-higress-migration.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 394 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.00099 | $0.03945 |
| Opus 5 | $0.00049 | $0.01972 |
| Sonnet 5 | $0.00020 | $0.00789 |
| Haiku 4.5 | $0.00010 | $0.00394 |
Grade A, and why
nginx-to-higress-migration 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -H "Host: example.com" http://localhost:8080/ How it starts
The opening of the file, as written. The whole thing — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nginx to Higress Migration
Automate migration from ingress-nginx to Higress in Kubernetes environments.
⚠️ Critical Limitation: Snippet Annotations NOT Supported
Before you begin: Higress does NOT support the following nginx annotations:
nginx.ingress.kubernetes.io/server-snippetnginx.ingress.kubernetes.io/configuration-snippetnginx.ingress.kubernetes.io/http-snippetThese annotations will be silently ignored, causing functionality loss!
Pre-migration check (REQUIRED):
kubectl get ingress -A -o yaml | grep -E "snippet" | wc -lIf count > 0, you MUST plan WASM plugin replacements before migration. See Phase 6 for alternatives.
Prerequisites
- kubectl configured with cluster access
- helm 3.x installed
- Go 1.24+ (for WASM plugin compilation)
- Docker (for plugin image push)
Pre-Migration Checklist
Before Starting
- Backup all Ingress resources
kubectl get ingress -A -o yaml > ingress-backup.yaml - Identify snippet usage (see warning above)
- List all nginx annotations in use
kubectl get ingress -A -o yaml | grep "nginx.ingress.kubernetes.io" | sort | uniq -c - Verify Higress compatibility for each annotation (see annotation-mapping.md)
- Plan WASM plugins for unsupported features
- Prepare test environment (Kind/Minikube for testing recommended)
During Migration
- Install Higress in parallel with nginx
- Verify all pods running in higress-system namespace
- Run test script against Higress gateway
- Compare responses between nginx and Higress
- Deploy any required WASM plugins
- Configure monitoring/alerting
After Migration
- All routes verified working
- Custom functionality (snippet replacements) tested
- Monitoring dashboards configured
- Team trained on Higress operations
- Documentation updated
- Rollback procedure tested
What ships with it
10 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.
- README_CN.md 14 KB
- README.md 15 KB
- references/annotation-mapping.md 7.6 KB
- references/builtin-plugins.md 4.0 KB
- references/plugin-deployment.md 5.4 KB
- references/snippet-patterns.md 8.1 KB
- scripts/analyze-ingress.sh 6.1 KB runs code
- scripts/generate-migration-test.sh 7.1 KB runs code
- scripts/generate-plugin-scaffold.sh 6.5 KB runs code
- scripts/install-harbor.sh 4.9 KB runs code
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 · 478 lines · 99 tokens per session scan A 504bf863b6f3
nginx-to-higress-migration is a skill published in the GitHub repository higress-group/higress (9,365 stars, last pushed yesterday), licensed Apache-2.0. It adds 99 tokens to every session and 3,945 once invoked, about $0.0005 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
ak-cloud-deploy
Deploy an Agent Kernel project to AWS, Azure, or GCP using Terraform modules, or to any Kubernetes cluster (on-prem, baremetal, EKS) using the official Helm chart. Supports serverless and containerized modes for all three clouds. AWS supports execution modes (restsync, restasync, async, stream), queue-based scalable…
openpitrix
KubeSphere OpenPitrix application management Skill. Use when users ask about KubeSphere App Store, OpenPitrix, Helm/YAML application templates, application repositories, app versions, app releases, categories, review states, repository sync, or troubleshooting application installation and upgrade issues.
kubesphere-openkruise
KubeSphere OpenKruise management Skill. Use when user asks to install or enable OpenKruise, check OpenKruise status, view kruise pods/logs/CRDs, create or update SidecarSet, manage sidecar injection, create or update CloneSet, perform in-place update or batch rollout, uninstall or remove OpenKruise, or troubleshoot…
kubesphere-volcano
KubeSphere Volcano job management Skill. Use when user asks to create, list, update, delete Jobs (Volcano Jobs), manage Queues, create PyTorch/TensorFlow/MPI training jobs, or troubleshoot Volcano scheduling issues in KubeSphere. Includes built-in YAML templates, scheduling policy recommendations, and best practices…
serverless-expert
Design and implement production-grade serverless applications with optimal performance, cost efficiency, and scalability. Use when the user mentions serverless or FaaS, AWS Lambda, Azure Functions, Cloud Functions, cold starts, event-driven architecture, or API Gateway-fronted workloads.
migration-patterns
Migrate workloads from Kubernetes, Docker Compose, or Helm to Control Plane. Use when the user asks to convert k8s manifests, a docker-compose.yml, or Helm charts, or to move an existing app onto the platform.