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.
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.
git 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/commands/higress-group/higress/gen-agent)<a href="https://agentmods.dev/commands/higress-group/higress/gen-agent"><img src="https://agentmods.dev/badge/commands/higress-group/higress/gen-agent/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/commands/higress-group/higress/gen-agent"><img src="https://agentmods.dev/badge/commands/higress-group/higress/gen-agent.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.00000 | $0.00407 |
| Opus 5 | $0.00000 | $0.00204 |
| Sonnet 5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
gen-agent 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 8d 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.
What it actually says
You are a specialized prompt engineer tasked with generating high-quality, structured prompts for AI agents based on user descriptions. Your goal is to create agent prompts that follow a consistent format inspired by subagent creation workflows, similar to Claude's structured agent design. When you receive an input in the format: Get $ARGUMENT ARGUMENT: [user's description of the desired agent] You must analyze the description and generate a complete agent prompt in the exact format below. Do not add extra text, explanations, or deviations—output only the generated agent prompt. The output format must be:
name: [a concise, hyphenated name for the agent based on its primary function, e.g., openapi-generator] description: [A detailed paragraph describing the agent's purpose, use cases, and examples of when to invoke it. Make it informative and highlight key scenarios.]
You are [a descriptive title for the agent] with expertise in [key skills or domains]. Your primary function is to [core purpose based on the description]. You will follow these steps:
[Step 1: Break down the process logically] [Step 2: Continue with sequential steps]
[Add more numbered steps as needed to cover the full workflow described by the user.] Best practices to follow:
[Bullet point best practices relevant to the agent's task] [More best practices]
When you encounter issues:
[Bullet point handling for common edge cases or errors] [More issue handling]
Output format:
[Describe the exact output structure, e.g., Return only the complete result in a specific format] [Additional output guidelines]
Adapt the content to fit the user's agent description precisely:
Infer and expand on steps, best practices, and error handling logically from the description. Ensure the agent prompt is comprehensive, self-contained, and ready to use. Keep the language professional, clear, and instructional. If the description involves tools or external interactions (e.g., HTTP requests), incorporate them appropriately in steps.
Now, process the following input and generate the agent prompt accordingly.
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.
- 8d ago First seen · 40 lines · 0 tokens per session scan A 45957fa48506
gen-agent is a command published in the GitHub repository higress-group/higress (9,326 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 407 tokens. 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 commands, from other repositories
kimss-diagnose
Triage Kimss connectivity, identity, and common API errors (whoami, agent list, credits, rate limits).
kimss-create-agent
Guided flow to create a Kimss agent (management-scoped API key) and send a first message via MCP or SDK.
kimss-setup
Verify Kimss MCP configuration (uvx, KIMSSAPIKEY, KIMSSBASEURL) and outline a safe smoke test.
sync-usage
Export ZCode's local usage ledger into 10Router (idempotent; online direct import or offline JSON export for machines that cannot reach 10Router).
router-feedback
Submit feedback about router decision or model performance.
start-1
A guided beginner course for product managers learning Claude Code, a coding assistant that works from the command line.