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-daily-report/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-daily-report)<a href="https://agentmods.dev/skills/higress-group/higress/higress-daily-report"><img src="https://agentmods.dev/badge/skills/higress-group/higress/higress-daily-report/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-daily-report"><img src="https://agentmods.dev/badge/skills/higress-group/higress/higress-daily-report.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.00050 | $0.01958 |
| Opus 5 | $0.00025 | $0.00979 |
| Sonnet 5 | $0.00010 | $0.00392 |
| Haiku 4.5 | $0.00005 | $0.00196 |
Grade A, and why
higress-daily-report 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 11d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Higress Daily Report
驱动 Higress 社区问题处理的智能工作流。
核心目标
- 每日感知 - 追踪新 issues/PRs 和评论动态
- 进度跟踪 - 确保每个 issue 被持续跟进直到关闭
- 知识沉淀 - 积累问题分析和解决方案,提升处理能力
- 闭环驱动 - 通过日报推动问题解决,避免遗忘
数据文件
| 文件 | 用途 |
|---|---|
/root/clawd/memory/higress-issue-tracking.json |
Issue 追踪状态(评论数、跟进状态) |
/root/clawd/memory/higress-knowledge-base.md |
知识库:问题模式、解决方案、经验教训 |
/root/clawd/reports/report_YYYY-MM-DD.md |
每日报告存档 |
工作流程
1. 获取每日数据
# 获取昨日 issues
gh search issues --repo alibaba/higress --created yesterday --json number,title,author,url,body,state,labels --limit 50
# 获取昨日 PRs
gh search prs --repo alibaba/higress --created yesterday --json number,title,author,url,body,state,additions,deletions,reviewDecision --limit 50
2. Issue 追踪状态管理
追踪数据结构 (higress-issue-tracking.json):
{
"date": "2026-01-28",
"issues": [
{
"number": 3398,
"title": "Issue 标题",
"state": "open",
"author": "username",
"url": "https://github.com/...",
"created_at": "2026-01-27",
"comment_count": 11,
"last_comment_by": "johnlanni",
"last_comment_at": "2026-01-28",
"follow_up_status": "waiting_user",
"follow_up_note": "等待用户提供请求日志",
"priority": "high",
"category": "cors",
"solution_ref": "KB-001"
}
]
}
跟进状态枚举:
new- 新 issue,待分析analyzing- 正在分析中waiting_user- 等待用户反馈waiting_review- 等待 PR reviewin_progress- 修复进行中resolved- 已解决(待关闭)closed- 已关闭wontfix- 不予修复stale- 超过 7 天无活动
3. 知识库结构
知识库 (higress-knowledge-base.md) 用于沉淀经验:
# Higress 问题知识库
## 问题模式索引
### 认证与跨域类
- KB-001: OPTIONS 预检请求被认证拦截
- KB-002: CORS 配置不生效
### 路由配置类
- KB-010: 路由状态 address 为空
- KB-011: 服务发现失败
### 部署运维类
- KB-020: Helm 安装问题
- KB-021: 升级兼容性问题
---
## KB-001: OPTIONS 预检请求被认证拦截
**问题特征**:
- 浏览器 OPTIONS 请求返回 401
- 已配置 CORS 和认证插件
**根因分析**:
Higress 插件执行阶段优先级:AUTHN (310) > AUTHZ (340) > STATS
- key-auth 在 AUTHN 阶段执行
- CORS 在 AUTHZ 阶段执行
- OPTIONS 请求先被 key-auth 拦截,CORS 无机会处理
**解决方案**:
1. **推荐**:修改 CORS 插件 stage 从 AUTHZ 改为 AUTHN
2. **Workaround**:创建 OPTIONS 专用路由,不启用认证
3. **Workaround**:使用实例级 CORS 配置
**关联 Issue**:#3398
**学到的经验**:
- 排查跨域问题时,首先确认插件执行顺序
- Higress 阶段优先级由 phase 决定,不是 priority 数值
What ships with it
2 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.
- 11d ago First seen · 258 lines · 50 tokens per session scan A d0712a94bd95
higress-daily-report is a skill published in the GitHub repository higress-group/higress (9,365 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 1,958 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
change-dispatch
Agent-agnostic task dispatcher. Reads backlog on main to find active changes, atomically claims one task group from an isolated worker branch, implements it, and pushes it to the shared feature branch. Runnable by Codex, Claude Code, cron, GitHub Actions, or one-shot runners with the project toolchain and credentials…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.