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 skills/jkaninda/okapi-skills/tls_httpsnpx skills add jkaninda/okapi-skills --skill tls_httpsgit clone --depth 1 https://github.com/jkaninda/okapi-skillsWhat 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.01012 |
| Opus 5 | $0.00000 | $0.00506 |
| Sonnet 5 | $0.00000 | $0.00202 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
tls_https 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 yesterday.
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 TLS & HTTPS
Loading a TLS Config
func okapi.LoadTLSConfig(certFile, keyFile, caFile string, clientAuth bool) (*tls.Config, error)
| Parameter | Description |
|---|---|
certFile |
Path to the certificate (PEM) |
keyFile |
Path to the private key (PEM) |
caFile |
Optional CA certificate for verifying client certs — "" disables |
clientAuth |
Require client certificate verification (mTLS) |
HTTPS-Only Server
tlsConfig, err := okapi.LoadTLSConfig("cert.pem", "key.pem", "", false)
if err != nil {
panic(err)
}
o := okapi.New(okapi.WithTLS(tlsConfig), okapi.WithAddr(":8443"))
o.Get("/", func(c *okapi.Context) error {
return c.OK(okapi.M{"status": "secure"})
})
o.Start() // ListenAndServeTLS
When the server's TLSConfig is set, Start() serves HTTPS on the configured address.
Dual HTTP + HTTPS
WithTLSServer runs a second listener with its own address, sharing the same routes and middleware:
tlsConfig, _ := okapi.LoadTLSConfig("cert.pem", "key.pem", "", false)
o := okapi.Default() // HTTP on :8080
o.With(okapi.WithTLSServer(":8443", tlsConfig)) // HTTPS on :8443
o.Start() // HTTP served in a goroutine, HTTPS in the foreground
Stop() / StopWithContext(ctx) gracefully shut down both listeners.
Mutual TLS (client certificates)
tlsConfig, err := okapi.LoadTLSConfig("server.crt", "server.key", "ca.crt", true)
o := okapi.New(okapi.WithTLS(tlsConfig))
With clientAuth: true, the CA in caFile verifies presented client certificates. Inspect the peer in a handler:
o.Get("/whoami", func(c *okapi.Context) error {
tls := c.Request().TLS
if tls == nil || len(tls.PeerCertificates) == 0 {
return c.AbortUnauthorized("client certificate required")
}
return c.OK(okapi.M{"cn": tls.PeerCertificates[0].Subject.CommonName})
})
Custom *tls.Config (autocert / Let's Encrypt)
The *Okapi struct has no exported fields, so supply a pre-built *http.Server instead of assigning to one:
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.
- yesterday First seen · 133 lines · 0 tokens per session scan A c517ccd029e8
tls_https is a skill published in the GitHub repository jkaninda/okapi-skills (3 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,012 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
advogado-especialista
Advogado especialista em todas as areas do Direito brasileiro: familia, criminal, trabalhista, tributario, consumidor, imobiliario, empresarial, civil e constitucional.
2slides-ppt-generator
AI-powered presentation generation via the 2slides API — create slides from text, match a reference image style, summarize documents into decks, add AI voice narration, and export pages/audio. Use for any "make slides", "create a deck", or "slides from this document" request.
agentic-actions-auditor
Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches. AI agents running in CI/CD pipelines.
ad-creative
Create, iterate, and scale paid ad creative for Google Ads, Meta, LinkedIn, TikTok, and similar platforms. Use when generating headlines, descriptions, primary text, or large sets of ad variations for testing and performance optimization.
agent-framework-azure-ai-py
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.