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-scheduling-quartzWrote 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-scheduling-quartz)<a href="https://agentmods.dev/skills/kora-projects/kora-skills/kora-aop-scheduling-quartz"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-aop-scheduling-quartz/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-scheduling-quartz"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-aop-scheduling-quartz.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.00065 | $0.02676 |
| Opus 5 | $0.00032 | $0.01338 |
| Sonnet 5 | $0.00013 | $0.00535 |
| Haiku 4.5 | $0.00006 | $0.00268 |
Grade A, and why
kora-aop-scheduling-quartz 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 11d 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kora Quartz Scheduling
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.
Annotation-driven scheduling backed by the Quartz library. Annotate a method on
a @Component with @ScheduleWithCron or @ScheduleWithTrigger; Kora generates
the aspect at compile time and registers the job with a Quartz Scheduler.
Use Quartz when you need cron expressions or a custom Quartz Trigger.
For simple fixed-rate / fixed-delay / one-shot timers, use the lighter
scheduling-jdk module instead — see kora-aop-scheduling-jdk.
Class requirement: the enclosing class must be a @Component. Kora generates
a separate Quartz Job wrapper at compile time, so the component class itself can
stay final (Java) / non-open (Kotlin) — the canonical examples use
public final class ...Scheduler. (The general "non-final/open" rule only
applies to AOP aspects that wrap the method body, such as @Log or @Retry.)
Quick Start
1. Dependencies
The kora-parent BOM pins every Kora artifact — never version ru.tinkoff.kora:*
deps yourself.
// build.gradle (Java)
dependencies {
koraBom platform("ru.tinkoff.kora:kora-parent:1.2.19")
annotationProcessor "ru.tinkoff.kora:annotation-processors" // mandatory
implementation "ru.tinkoff.kora:scheduling-quartz"
implementation "ru.tinkoff.kora:config-hocon"
implementation "ru.tinkoff.kora:logging-logback"
}
// build.gradle.kts (Kotlin)
dependencies {
koraBom(platform("ru.tinkoff.kora:kora-parent:1.2.19"))
ksp("ru.tinkoff.kora:symbol-processors") // mandatory
implementation("ru.tinkoff.kora:scheduling-quartz")
implementation("ru.tinkoff.kora:config-hocon")
implementation("ru.tinkoff.kora:logging-logback")
}
What ships with it
9 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/ScheduledJobs.java.template 2.6 KB
- assets/ScheduledJobs.kt.template 2.2 KB
- evals/evals.json 5.0 KB
- references/graceful-shutdown-reference.md 3.8 KB
- references/quartz-scheduling-reference.md 7.2 KB
- references/scheduling-config-reference.md 4.5 KB
- scripts/create-cron-job.sh 2.0 KB runs code
- scripts/setup-quartz.sh 3.1 KB runs code
- scripts/validate-cron.sh 2.6 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.
- 11d ago First seen · 331 lines · 65 tokens per session scan A b9f16af1e4ed
kora-aop-scheduling-quartz is a skill published in the GitHub repository kora-projects/kora-skills (1 stars, last pushed 10d ago), licensed Apache-2.0. It adds 65 tokens to every session and 2,676 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.