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 jkaninda/okapi-skills --skill request_bindinggit clone --depth 1 https://github.com/jkaninda/okapi-skillsWrote 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/jkaninda/okapi-skills/request_binding)<a href="https://agentmods.dev/skills/jkaninda/okapi-skills/request_binding"><img src="https://agentmods.dev/badge/skills/jkaninda/okapi-skills/request_binding/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/jkaninda/okapi-skills/request_binding"><img src="https://agentmods.dev/badge/skills/jkaninda/okapi-skills/request_binding.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.00000 | $0.01255 |
| Opus 5.5 | $0.00000 | $0.00502 |
| Sonnet 5.5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
request_binding 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 1mo 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Okapi Request Binding
Binding populates a struct from the request by inspecting struct tags and the Content-Type. Validation runs automatically at the end of c.Bind — the tags are documented in the validation/ skill.
Source Tags
| Tag | Source | Example |
|---|---|---|
json:"name" |
JSON body | Name string `json:"name"` |
xml:"name" |
XML body | Name string `xml:"name"` |
yaml:"name" |
YAML body | Name string `yaml:"name"` |
form:"name" |
Form field / uploaded file | File *multipart.FileHeader `form:"file"` |
query:"page" |
Query parameter | Page int `query:"page"` |
path:"id" / param:"id" |
Path parameter | ID int `path:"id"` |
header:"X-Key" |
Request header | Key string `header:"X-API-Key"` |
cookie:"session" |
Cookie | Sess string `cookie:"session"` |
Source tags combine on one field — the body is decoded first, then path/query/form/header/cookie values are overlaid:
type BookInput struct {
ID int `json:"id" path:"id"`
Name string `json:"name" form:"name" query:"name"`
Price int `json:"price" form:"price" query:"price"`
}
Two Binding Styles
1. Flat binding — body fields sit alongside query/header/cookie/path fields in one struct.
2. Body-field binding (recommended) — a field named Body (or tagged json:"body") holds the payload; sibling fields carry metadata. The presence of such a field switches c.Bind to this mode.
type CreateBookRequest struct {
Body struct { // request payload
Name string `json:"name" required:"true" minLength:"2"`
Price int `json:"price" required:"true" min:"5"`
}
BookID string `path:"bookId" required:"true"` // path parameter
Tags []string `query:"tags"` // query parameter
APIKey string `header:"X-API-Key" required:"true"` // header
SessionID string `cookie:"SessionID"` // cookie
}
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.
- 1mo ago First seen · 133 lines · 0 tokens per session scan A 56f0c15ac93e
request_binding is a skill published in the GitHub repository jkaninda/okapi-skills (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,255 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 skills, from other repositories
telnyx-iot-curl
Manage IoT SIM cards, eSIMs, data plans, and wireless connectivity. Use when building IoT/M2M solutions. This skill provides REST API (curl) examples.
telnyx-porting-in-curl
Port phone numbers into Telnyx. Check portability, create port orders, upload LOA documents, and track porting status. This skill provides REST API (curl) examples.
telnyx-networking-curl
Configure private networks, WireGuard VPN gateways, internet gateways, and virtual cross connects. This skill provides REST API (curl) examples.
telnyx-sip-curl
Configure SIP trunking connections and outbound voice profiles. Use when connecting PBX systems or managing SIP infrastructure. This skill provides REST API (curl) examples.
telnyx-twilio-migration
Migrate from Twilio to Telnyx. Orchestrates a complete 6-phase migration: discovery, planning, setup, code migration, validation, and cleanup. Covers voice (TwiML to TeXML, Call Control API), messaging, WebRTC, SIP trunking, verify, fax, video, IoT, number lookup, and porting. Includes automated scanners, validation…
telnyx-ai-inference-curl
Access Telnyx LLM inference APIs, embeddings, and AI analytics for call insights and summaries. This skill provides REST API (curl) examples.