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-clientWrote 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-client)<a href="https://agentmods.dev/skills/kora-projects/kora-skills/kora-http-client"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-http-client.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.00069 | $0.03318 |
| Opus 5 | $0.00034 | $0.01659 |
| Sonnet 5 | $0.00014 | $0.00664 |
| Haiku 4.5 | $0.00007 | $0.00332 |
Grade A, and why
kora-http-client 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kora HTTP Client
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.
Declarative, compile-time HTTP clients: annotate an interface with @HttpClient, declare methods with @HttpRoute, and the annotation processor generates the implementation. No reflection, no runtime proxies. Inject the client interface like any other Kora component.
Dependencies: http-client-ok (transport) + json-module (for @Json) + annotation-processors.
All Kora artifacts inherit their version from the ru.tinkoff.kora:kora-parent BOM (the examples pin 1.2.19). Never version individual ru.tinkoff.kora:* artifacts.
Quick Start
1. Dependencies (Java)
dependencies {
koraBom platform("ru.tinkoff.kora:kora-parent:1.2.19")
annotationProcessor "ru.tinkoff.kora:annotation-processors"
implementation "ru.tinkoff.kora:http-client-ok"
implementation "ru.tinkoff.kora:json-module"
implementation "ru.tinkoff.kora:config-hocon"
}
For Kotlin, use ksp "ru.tinkoff.kora:symbol-processors" instead of annotationProcessor.
2. Plug the transport module into @KoraApp
@KoraApp
public interface Application extends
HoconConfigModule,
JsonModule,
OkHttpClientModule {
}
3. Declare the client interface
@HttpClient(configPath = "httpClient.userApi")
public interface UserApiClient {
@HttpRoute(method = HttpMethod.GET, path = "/users/{userId}")
@Json
UserResponse getUser(@Path String userId);
@HttpRoute(method = HttpMethod.GET, path = "/users")
@Json
List<UserResponse> listUsers(@Query("page") int page, @Query("size") int size);
@HttpRoute(method = HttpMethod.POST, path = "/users")
@Json
HttpResponseEntity<UserResponse> createUser(@Json CreateUserRequest request);
@HttpRoute(method = HttpMethod.DELETE, path = "/users/{userId}")
void deleteUser(@Path String userId);
}
What ships with it
12 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/ApiKeyAuthInterceptor.java.template 1.9 KB
- assets/AsyncApiClient.java.template 2.6 KB
- assets/CustomMapperClient.java.template 4.9 KB
- assets/ResilientApiClient.java.template 3.3 KB
- assets/UserApiClient.java.template 2.2 KB
- assets/UserApiClient.kt.template 2.2 KB
- evals/evals.json 6.6 KB
- references/async-client-reference.md 6.6 KB
- references/declarative-client-reference.md 9.9 KB
- references/error-handling-guide.md 7.2 KB
- references/interceptors-reference.md 7.2 KB
- references/okhttp-transport-reference.md 5.9 KB
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 · 329 lines · 69 tokens per session scan A c46e4ed72c7f
kora-http-client is a skill published in the GitHub repository kora-projects/kora-skills (1 stars, last pushed 7d ago), licensed Apache-2.0. It adds 69 tokens to every session and 3,318 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-lazarus-compatibility
Guide for ensuring Lazarus and Free Pascal (FPC) compatibility, addressing anonymous methods differences, JSON units, and compiler directives.
horse-performance-tuning
Guide for optimizing performance, tuning memory alocations, handling large payloads, and adjusting provider execution pipelines.