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-wasm-go-plugin/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-wasm-go-plugin)<a href="https://agentmods.dev/skills/higress-group/higress/higress-wasm-go-plugin"><img src="https://agentmods.dev/badge/skills/higress-group/higress/higress-wasm-go-plugin/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-wasm-go-plugin"><img src="https://agentmods.dev/badge/skills/higress-group/higress/higress-wasm-go-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.01775 |
| Opus 5 | $0.00026 | $0.00888 |
| Sonnet 5 | $0.00010 | $0.00355 |
| Haiku 4.5 | $0.00005 | $0.00178 |
Grade A, and why
higress-wasm-go-plugin 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Higress WASM Go Plugin Development
Develop Higress gateway WASM plugins using Go language with the wasm-go SDK.
Quick Start
Project Setup
# Create project directory
mkdir my-plugin && cd my-plugin
# Initialize Go module
go mod init my-plugin
# Set proxy (China)
go env -w GOPROXY=https://proxy.golang.com.cn,direct
# Download dependencies
go get github.com/higress-group/[email protected]
go get github.com/higress-group/wasm-go@main
go get github.com/tidwall/gjson
Minimal Plugin Template
package main
import (
"github.com/higress-group/wasm-go/pkg/wrapper"
"github.com/higress-group/proxy-wasm-go-sdk/proxywasm"
"github.com/higress-group/proxy-wasm-go-sdk/proxywasm/types"
"github.com/tidwall/gjson"
)
func main() {}
func init() {
wrapper.SetCtx(
"my-plugin",
wrapper.ParseConfig(parseConfig),
wrapper.ProcessRequestHeaders(onHttpRequestHeaders),
)
}
type MyConfig struct {
Enabled bool
}
func parseConfig(json gjson.Result, config *MyConfig) error {
config.Enabled = json.Get("enabled").Bool()
return nil
}
func onHttpRequestHeaders(ctx wrapper.HttpContext, config MyConfig) types.Action {
if config.Enabled {
proxywasm.AddHttpRequestHeader("x-my-header", "hello")
}
return types.HeaderContinue
}
Compile
go mod tidy
GOOS=wasip1 GOARCH=wasm go build -buildmode=c-shared -o main.wasm ./
Core Concepts
Plugin Lifecycle
- init() - Register plugin with
wrapper.SetCtx() - parseConfig - Parse YAML config (auto-converted to JSON)
- HTTP processing phases - Handle requests/responses
HTTP Processing Phases
| Phase | Trigger | Handler |
|---|---|---|
| Request Headers | Gateway receives client request headers | ProcessRequestHeaders |
| Request Body | Gateway receives client request body | ProcessRequestBody |
| Response Headers | Gateway receives backend response headers | ProcessResponseHeaders |
| Response Body | Gateway receives backend response body | ProcessResponseBody |
| Stream Done | HTTP stream completes | ProcessStreamDone |
What ships with it
4 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.
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 · 252 lines · 52 tokens per session scan A 9d37e8d831c0
higress-wasm-go-plugin is a skill published in the GitHub repository higress-group/higress (9,365 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 1,775 once invoked, about $0.0003 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
hecate-providers
Use when working in internal/providers/ — outbound HTTP adapters to LLM upstreams (OpenAI-compat, Anthropic). Owns the api↔providers parallel-struct boundary and the seven-step "add a wire field" chain.
new-mq-consumer
A skill that generates a message-queue consumer for a Go service from its scheduled-task design. A message queue delivers events between services, and a consumer reads those events; this one is designed to batch them, store them, update Redis, and send failures to a dead-letter queue.
go
Use when writing Go/Golang code — goroutines/channels concurrency, net/http web servers, database/sql, generics (1.18+), module management, testing and benchmarking. Go: the language powering Docker, Kubernetes, and cloud-native infrastructure.
golang-graphql
Implements GraphQL APIs in Golang using gqlgen or graphql-go. Apply when building GraphQL servers, designing schemas, writing resolvers, handling subscriptions, or integrating GraphQL with existing Go HTTP services. Also apply when the codebase imports github.com/99designs/gqlgen or github.com/graph-gophers/graphql-go.
golang-pro
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming…
golang-grpc
Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or…