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.
npx agentmods add rules/higress-group/higress/plugin-developmentgit clone --depth 1 https://github.com/higress-group/higressWhat 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 | $0.00000 | $0.00809 |
| Opus 5 | $0.00000 | $0.00404 |
| Sonnet 5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
plugin-development 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 today.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Development Standards
These rules apply when creating or materially changing a Wasm or golang-filter
plugin. Follow the repository-wide build and test guidance in
AGENTS.md and the
contributor guide.
Agent participation and issue-spec gate
Before implementation, determine whether an AI or coding agent will materially participate under the agent-assisted contribution policy. When material participation applies:
- enter the Higress issue-spec workflow before implementation begins;
- do not begin implementation until a Higress maintainer has approved the Proposal Issue and Design Issue;
- implement only through TASKs authorized by the approved Design and preserve traceability to the applicable SPECs;
- ensure the Design contains a concrete Verification Plan before verification begins; and
- complete the applicable implementation and verification TASKs with commands, results, evidence links, and hashes before asking maintainers to accept the verification or review.
The maintainer-approved issue-spec Design Issue is the authoritative design
carrier. No plugin-local design/ directory, design document, or AI prompt file
is required for this gate, and none should be created or required as a
substitute for the approved Design Issue.
Disclose the prompts or instructions given to the agent and provide an
AI-assisted work summary in the pull request template, with secrets and
sensitive data removed. Human-only work is outside this agent gate. The narrow
trivial-edit exception is defined in the canonical policy and must be declared
when used. A canonical-repository maintainer or administrator may use the
verified maintainer/administrator exception only after completing the canonical
policy's authenticated gh identity and collaborator-permission checks and
recording the login, returned role_name of maintain or admin, and bypass
rationale in the PR. The current PR author must match the verified login. This
must include a positive attestation that both GH_TOKEN and GITHUB_TOKEN
were unset for every verification command and fail closed on a missing, failed,
or mismatched check; the accepting or merging maintainer independently validates
current live evidence with token overrides unset. This does not waive bug-fix
runtime verification.
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.
- today First seen · 80 lines · 0 tokens per session scan A 62fdcb379e69
plugin-development is a cursor rule published in the GitHub repository higress-group/higress (9,250 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 809 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 cursor rules, from other repositories
kimss-product
Kimss product and API conventions when integrating the gateway, MCP, or the Python control-plane package in Cursor.
architecture-vault
Source of truth: this directory lives under private monorepo kimssApi/kimsssdk/. The public kimss-python-sdk repo is a git subtree force-push mirror. Never treat the public main as an editable SSOT.
cursorrules
Follow AIINTEGRATION.md.
binding-rules-quick-reference
Quick index of project binding rules (canonical text in CLAUDE.md).
go-conventions
Go conventions for all Go code (modules, naming, errors, logging, metrics).
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.