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-platform-routergit 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-platform-router)<a href="https://agentmods.dev/skills/kong/ai-marketplace/konnect-platform-router"><img src="https://agentmods.dev/badge/skills/kong/ai-marketplace/konnect-platform-router/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-platform-router"><img src="https://agentmods.dev/badge/skills/kong/ai-marketplace/konnect-platform-router.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.00053 | $0.01476 |
| Opus 5 | $0.00026 | $0.00738 |
| Sonnet 5 | $0.00011 | $0.00295 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
konnect-platform-router 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Konnect platform router
Goal
Turn broad Konnect requests into one primary downstream skill with a clear next step and one concrete thing that skill should prove next.
Use this skill as a classifier and handoff layer. Do not turn it into a product guide or a second copy of specialist workflows.
Shared Operating Defaults
- Prefer the shared
kong-konnectMCP server when the request depends on live Konnect state. - If
kong-konnectMCP is unavailable, say so early and continue withkongctl-query, repository artifacts, logs, or user-provided state. - Preserve the repository's existing declarative toolchain. Do not convert the
user between
decK,kongctl, and Terraform unless they ask. - Prefer current live state and current product docs over stale assumptions when behavior, product coverage, or limits may have changed.
- When a downstream CLI appears blocked by the agent environment, let the specialist tool skill handle sandbox retry guidance instead of classifying it as a product failure here.
These defaults are intentionally short. Specialist skills may restate the same guidance because they can trigger directly without this router.
Classification Order
1. Decide whether routing is needed at all
Bypass this router when the request already has one obvious owner.
Hand off directly when the user already named:
- a specialist workflow such as gateway triage, API publication, Event Gateway, or AI Gateway
- a declarative toolchain such as
kongctl, Terraform, ordecK - a repo-authoring task that belongs to
kong-skill-authoringrather than a Konnect product workflow
Use this router only when the request is broad, cross-surface, or still ambiguous after the first read.
2. Decide whether this is diagnosis, inspection, or implementation
Classify the user's immediate need first:
- diagnosing current Konnect behavior
- asking for exact read-only inspection
- planning or authoring declarative changes
- asking which domain owns the problem
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 · 174 lines · 53 tokens per session scan A 4dc6b4ff2535
konnect-platform-router is a skill published in the GitHub repository Kong/ai-marketplace (5 stars, last pushed 21d ago), licensed MIT. It adds 53 tokens to every session and 1,476 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
agent-communication-protocol
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks.
pre-merge
The CI gate. Takes a feature branch from "eng says done" to "PR open against staging with green checks". Runs the project's preflight-resolved pipeline from devkit/policy.json components[]: sync → parallel correctness + security waves → coverage → regression tail → security/migration → PRD-consistency → open PR. Emits…
intake
The planning front-door. Captures feature ideas and bugs as graded rows in the root INTAKE.md ledger. Use it when the user says "log an idea", "capture a bug", "add to the backlog", "note this down", "track this feature", or invokes /intake. Owns the requirements interview — fleshes out thin ideas, proactively…
merge
The ship gate — the only skill that merges. --staging merges the feature→staging PR on green CI, deploys, verifies, emits a human test script and stamps the staging sign-off on approval. --production ships the double-confirmed release to main and deploys production. Never self-certifies staging; nothing reaches main…
msg
Root menu for msg skills, plus harness modes. --init is the one-time project bootstrap — use it when the user says "initialise project", "bootstrap repo", "set up the framework", "start a new project", or asks to set up project structure in an empty repo. Other modes: --init-staging (add a staging branch), --update…
plan-pm
Principal PM skill — the autonomous PRD writer. Consumes a graded, fleshed-out row from the INTAKE.md backlog (idea, goal, type, grade) and drafts the full PRD solo — feature/acceptance table, edge cases, error handling — saved to features/planned/prd-[n]-[feature-slug]/. The requirements interview lives in /intake…