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 skills add Kong/ai-marketplace --skill konnect-event-gatewaygit clone --depth 1 https://github.com/Kong/ai-marketplaceWrote 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/kong/ai-marketplace/konnect-event-gateway)<a href="https://agentmods.dev/skills/kong/ai-marketplace/konnect-event-gateway"><img src="https://agentmods.dev/badge/skills/kong/ai-marketplace/konnect-event-gateway/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/kong/ai-marketplace/konnect-event-gateway"><img src="https://agentmods.dev/badge/skills/kong/ai-marketplace/konnect-event-gateway.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.00052 | $0.01412 |
| Opus 5 | $0.00026 | $0.00706 |
| Sonnet 5 | $0.00010 | $0.00282 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
konnect-event-gateway 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event Gateway operator workflow
Goal
Troubleshoot Event Gateway using its own entity model instead of forcing it into standard gateway assumptions.
Default to following the request path end to end: client -> listener -> virtual cluster -> backend cluster -> policy and auth
Own the diagnosis of the failing Event Gateway hop. Hand off implementation or non-Event-Gateway platform problems once that hop is clear.
Tool Selection
- Use the shared
kong-konnectMCP server first for live Event Gateway inspection. - Use
kongctl-queryfor read-only resource checks and concise summaries where the CLI surface is available. - Preserve the repository's chosen declarative toolchain when Event Gateway
resources need to change. Prefer
kongctl-declarativeforkongctlYAML andterraform-konnectwhen the required Event Gateway resources are already managed in HCL. - Hand off early to
konnect-gateway-triagewhen the blocker is generic control-plane, data-plane, or rollout health rather than Event Gateway path semantics. - If live Konnect state matters and
kong-konnectMCP is not connected, say so early and continue with CLI or user-provided artifacts.
Do not reuse generic gateway triage blindly. Event Gateway deserves a dedicated inspection order because the operator objects differ.
References To Load
Load only the reference file that matches the active branch:
references/event-path-map.md- Load when the operator only has a symptom and you need to map the failing hop across listener, virtual cluster, backend cluster, auth, and policy.
references/listener-and-hostname-mapping.md- Load when the likely issue is listener reachability, hostname mapping, TLS, or protocol assumptions.
references/cluster-routing-boundaries.md- Load when virtual-cluster to backend-cluster routing intent is the hard part.
references/auth-and-policy-order.md- Load when clients connect but get denied, rewritten, or otherwise fail after reachability is already proven.
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 · 191 lines · 52 tokens per session scan A 3ef5adc7b6cb
konnect-event-gateway is a skill published in the GitHub repository Kong/ai-marketplace (5 stars, last pushed 22d ago), licensed MIT. It adds 52 tokens to every session and 1,412 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
error-handling-patterns
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
eve
Build durable backend AI agents with the eve framework. Use when creating, editing, or debugging an eve project — agent instructions, skills, tools, connections, channels, sandboxes, subagents, schedules, or evals.
azure-messaging
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue…
agent-communication-protocol
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks.
iii-error-handling
Handle iii engine and SDK errors across Node, Python, Rust, and browser workers. Use when interpreting error codes, retryability, RBAC denial, timeouts, handler failures, or SDK-specific exception surfaces.
database-rds-devops
Database-level data-plane diagnostics for Aurora MySQL and Aurora PostgreSQL. Executes predefined read-only health check queries via RDS Data API to analyze buffer pool, connections, locks, replication, storage, performance, and index efficiency. Requires the rds-aidba MCP server for database-internal access beyond…