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 usetheokit/theokit --skill theokit-gatewaysgit clone --depth 1 https://github.com/usetheokit/theokitWrote 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/usetheokit/theokit/theokit-gateways)<a href="https://agentmods.dev/skills/usetheokit/theokit/theokit-gateways"><img src="https://agentmods.dev/badge/skills/usetheokit/theokit/theokit-gateways/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/usetheokit/theokit/theokit-gateways"><img src="https://agentmods.dev/badge/skills/usetheokit/theokit/theokit-gateways.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.00039 | $0.01139 |
| Opus 5 | $0.00019 | $0.00570 |
| Sonnet 5 | $0.00008 | $0.00228 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
theokit-gateways 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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TheoKit Gateways
Receiving a message from a messaging platform spans three packages, and each owns one part of it.
| Package | Its half |
|---|---|
theokit (here) |
The HTTP route and the signature check. handleChannelWebhook verifies the signature, parses the body, and hands your app the parsed JSON as payload: unknown |
@theokit/gateway-* |
Translating that payload into a canonical event, so your app never re-declares a platform's wire format |
@theokit/sdk |
Not involved in this path today |
Wiring one
handleChannelWebhook is not mounted for you. It takes a Request, the URL path, and a config, and
returns the Response your route must return.
import { handleChannelWebhook } from 'theokit/server/agent'
import { telegram } from 'theokit/server/webhook' // also: discord, slack, github, stripe, whatsapp
import { parseInbound } from '@theokit/gateway-telegram'
const response = await handleChannelWebhook(request, new URL(request.url).pathname, {
validators: { telegram: telegram({ secretToken: process.env.TELEGRAM_SECRET_TOKEN! }) },
onMessage: async ({ agent, platform, payload }) => {
const event = parseInbound(payload)
if (event === null) return // not a message this adapter handles — see below
// hand `event` to your agent
},
})
The path it expects is POST /api/agents/<name>/channels/<platform>/webhook; <name> and
<platform> arrive in onMessage as agent and platform.
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.
- 4d ago Changed 6af1ab0a2d42
- 9d ago First seen · 100 lines · 39 tokens per session scan A 72e21470d44b
theokit-gateways is a skill published in the GitHub repository usetheokit/theokit (5 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 1,139 once invoked, about $0.0002 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
continuum-tools-mcp
Connect MCP servers (Stdio/SSE/StreamableHTTP) to a Continuum agent, configure tool filtering, set up tool-context capture/injection (e.g. sessionid), and read run artifacts (UI widgets, structured tool data). Invoke when the user asks "connect MCP", "filesystem tool", "remote API tool", "auto-capture sessionid"…
APIDesignArchitect
Complete API design intelligence — REST, GraphQL, gRPC, webhooks, API versioning, authentication, rate limiting, API governance, and building APIs that developers love and never want to leave.
DeveloperExperienceOS
Complete developer experience intelligence — SDK design, documentation, onboarding, developer community, API ergonomics, CLI tooling, and building products that developers love and evangelize.
StartupCTO
Complete CTO intelligence for early-stage startups — tech stack decisions, architecture, team building, technical debt management, and scaling from 0 to 10M users.
senior-dev
Activates the SeniorDev agent for full-stack software engineering. Use this skill when you need production-ready code: Next.js 14 frontends, FastAPI backends, TypeScript strict-mode components, PostgreSQL schemas, Redis caching, authentication flows, or complete REST/GraphQL APIs. SeniorDev always outputs complete…
system-architect
Activates SystemArchitect for high-level software system design and architecture review. Use when you need to design a new system from scratch (define components, APIs, data flows), review an existing architecture for scalability or reliability issues, choose between architectural patterns (monolith vs microservices…