Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/kora-projects/kora-skillsnpx agentmods add skills/kora-projects/kora-skills/kora-http-server-authWrote 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/kora-projects/kora-skills/kora-http-server-auth)<a href="https://agentmods.dev/skills/kora-projects/kora-skills/kora-http-server-auth"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-http-server-auth.svg" alt="Measured on agentmods" 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.00057 | $0.02795 |
| Opus 5 | $0.00028 | $0.01398 |
| Sonnet 5 | $0.00011 | $0.00559 |
| Haiku 4.5 | $0.00006 | $0.00280 |
Grade A, and why
kora-http-server-auth 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 7d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kora HTTP Server Auth
Kora sub-skill — obey the kora-v1 meta rules on every task: R0 ensure
.kora-agent/docs+examples are cloned · R1 read this sub-skill before writing code · R2 Kora APIs only — no Spring/Micronaut/Quarkus, no invented annotations or config keys · R3 journal any incorrect Kora usage. Add comments/Javadoc only if asked.
Authenticate and authorize Kora HTTP server endpoints. Kora has no @Secured-style
annotation and no thread-local "current user". Authentication is implemented in one of
two ways:
- OpenAPI-driven (preferred when you generate the server from a contract):
implement
HttpServerPrincipalExtractor<P>and bind it with@Tag(ApiSecurity.<Scheme>.class). The generated controller invokes the matching extractor before your delegate runs. - Manual (no OpenAPI contract): an
HttpServerInterceptorvalidates credentials and short-circuits, and/or anHttpServerRequestMapper<P>turns the request into a typed argument injected via@Mapping.
All Kora artifacts inherit the version from the kora-parent BOM (1.2.19 in
.kora-agent/kora-examples). Never pin individual ru.tinkoff.kora:* versions.
Quick Start (OpenAPI security)
1. Dependencies
dependencies {
koraBom platform("ru.tinkoff.kora:kora-parent:1.2.19")
annotationProcessor "ru.tinkoff.kora:annotation-processors" // mandatory: generates the graph + controllers
implementation "ru.tinkoff.kora:http-server-undertow"
implementation "ru.tinkoff.kora:json-module"
implementation "ru.tinkoff.kora:config-hocon"
implementation "ru.tinkoff.kora:logging-logback"
}
The OpenAPI kora generator produces the ApiSecurity class (one nested marker per
securityScheme) from the contract's components.securitySchemes. See
kora-openapi-generator-server for the
generator wiring.
2. Declare the security scheme in the contract
security:
- apiKeyAuth: [ ] # apply globally to every operation
components:
securitySchemes:
apiKeyAuth:
type: apiKey
in: header
name: Authorization
What ships with it
8 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.
- assets/ApiKeyExtractor.java.template 1.6 KB
- assets/ApiKeyExtractor.kt.template 1.5 KB
- assets/BasicAuthExtractor.java.template 2.0 KB
- assets/BasicAuthExtractor.kt.template 1.9 KB
- evals/evals.json 6.1 KB
- references/manual-auth-reference.md 6.8 KB
- references/openapi-security-reference.md 9.9 KB
- scripts/setup.sh 1.9 KB runs code
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.
- 7d ago First seen · 271 lines · 57 tokens per session scan A a63982ec60d7
kora-http-server-auth is a skill published in the GitHub repository kora-projects/kora-skills (1 stars, last pushed 7d ago), licensed Apache-2.0. It adds 57 tokens to every session and 2,795 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
horse-database-pooling
Guide for setting up thread-safe database connection pooling (FireDAC / UniDAC) in multithreaded Horse applications.
horse-mvc-architecture
Guide for structuring corporate Horse applications using Clean MVC (Model-View-Controller) principles and decoupling HTTP layers from business logic.
horse-request-response
Guide to interacting with THorseRequest (body, query, params, headers) and THorseResponse (Send, Status, ContentType).
horse-dependency-injection
Guide for managing request-scoped contextual services and IoC (dependency injection) in Delphi and Lazarus.
horse-performance-tuning
Guide for optimizing performance, tuning memory alocations, handling large payloads, and adjusting provider execution pipelines.
horse-ssl-tls
Guide to enabling SSL/TLS, configuring HTTPS, handling certificates, and securing transport layers.