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-aop-cachingWrote 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-aop-caching)<a href="https://agentmods.dev/skills/kora-projects/kora-skills/kora-aop-caching"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-aop-caching/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/kora-projects/kora-skills/kora-aop-caching"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-aop-caching.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.00058 | $0.02366 |
| Opus 5 | $0.00029 | $0.01183 |
| Sonnet 5 | $0.00012 | $0.00473 |
| Haiku 4.5 | $0.00006 | $0.00237 |
Grade A, and why
kora-aop-caching 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 10d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kora AOP Caching Skill
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.
Focus: Declarative caching via compile-time AOP annotations for Caffeine (in-process) and Redis (distributed) caches.
Read this first when:
- Adding cache to methods with
@Cacheable,@CachePut,@CacheInvalidate - Configuring Caffeine or Redis cache backends
- Creating custom cache key mappers with
CacheKeyMapper - Setting up multi-level caching (L1 Caffeine + L2 Redis)
Quick Start
1. Add Dependencies
All Kora artifacts inherit their version from the kora-parent BOM, so never pin a
version on a ru.tinkoff.kora:* dependency. The annotation processor is mandatory -
without it the @Cache/@Cacheable aspects and the typed cache implementation are
never generated.
dependencies {
koraBom platform("ru.tinkoff.kora:kora-parent:$koraVersion") // e.g. 1.2.19
annotationProcessor "ru.tinkoff.kora:annotation-processors" // Kotlin: ksp "ru.tinkoff.kora:symbol-processors"
// Local cache (Caffeine) - recommended for most cases
implementation "ru.tinkoff.kora:cache-caffeine"
// Or distributed cache (Redis/Lettuce) - for multi-pod shared state
// implementation "ru.tinkoff.kora:cache-redis"
}
2. Enable in Application
@KoraApp
public interface Application extends CaffeineCacheModule {}
// Or for Redis: extends RedisCacheModule
// Or for multi-level: extends CaffeineCacheModule, RedisCacheModule
3. Declare Typed Cache
@Cache("orders.cache.config")
public interface OrderCache extends CaffeineCache<UUID, OrderDto> {}
4. Use Cache Annotations
@Component
public class OrdersService {
@Cacheable(OrderCache.class)
public OrderDto get(UUID id) {
return repository.find(id);
}
@CachePut(value = OrderCache.class, parameters = { "id" })
public OrderDto update(UUID id, OrderDto dto) {
return repository.save(id, dto);
}
@CacheInvalidate(OrderCache.class)
public void delete(UUID id) {
repository.delete(id);
}
}
What ships with it
11 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/CacheConfig.java.template 5.8 KB
- assets/CacheConfig.kt.template 5.7 KB
- assets/OrderCache.java.template 10 KB
- assets/OrderCache.kt.template 9.8 KB
- evals/evals.json 7.3 KB
- references/cache-caffeine-reference.md 6.4 KB
- references/cache-key-mapper-reference.md 5.4 KB
- references/cache-redis-reference.md 8.0 KB
- references/cacheable-reference.md 6.6 KB
- references/imperative-cache-reference.md 7.5 KB
- references/multi-level-cache-reference.md 7.4 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.
- 10d ago First seen · 288 lines · 58 tokens per session scan A e8c0e73de928
kora-aop-caching is a skill published in the GitHub repository kora-projects/kora-skills (1 stars, last pushed 9d ago), licensed Apache-2.0. It adds 58 tokens to every session and 2,366 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.
spring-data-redis
Use when implementing caching, session storage, rate limiting, or any Redis integration. Covers cache-aside pattern, key naming, TTL strategy, and serialization config.
background-job-orchestrator
Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues. Implements retries, scheduling, priority queues, and worker management. Use for async task processing, email campaigns, report generation, batch operations. Activate on "background job", "async task", "queue", "worker", "BullMQ"…
nw-sd-patterns
Core distributed systems patterns - load balancing, caching, sharding, consistent hashing, message queues, rate limiting, CDN, Bloom filters, ID generation, replication, conflict resolution, CAP theorem.
cache-strategy
Design and implement caching layers for APIs and web applications using Redis or Memcached. Use when you need to reduce database load, improve response times, or handle traffic spikes. Covers cache-aside, write-through, and write-behind patterns, TTL strategies, cache invalidation, and stampede prevention. Trigger…
bull-mq
You are an expert in BullMQ, the high-performance job queue for Node.js built on Redis. You help developers build reliable background processing systems with delayed jobs, rate limiting, prioritization, repeatable cron jobs, job dependencies, concurrency control, and dead-letter handling — powering email sending…