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-dbWrote 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-db)<a href="https://agentmods.dev/skills/kora-projects/kora-skills/kora-aop-scheduling-db"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-aop-scheduling-db/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-db"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-aop-scheduling-db.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.00245 | $0.06640 |
| Opus 5.5 | $0.00098 | $0.02656 |
| Sonnet 5.5 | $0.00049 | $0.01328 |
| Haiku 4.5 | $0.00024 | $0.00664 |
Grade A, and why
kora-aop-scheduling-db 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 16d 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 — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kora AOP Scheduling (DB)
Kora sub-skill — obey the kora-v2 meta rules on every task: R0 ground the workspace on Kora 2.0 refs before starting (framework source at tag
2.0.0.RC2+kora-examplesatmigration/2.0+ Kora 2.0 docs at koraframework.io/v2, which trail the source; 1.xkora-docspages are never an authority) · R1 read this sub-skill before writing code · R2 Kora 2.0 APIs only — no Spring/Micronaut/Quarkus, no Kora 1.x APIs, no invented annotations or config keys · R3 journal any incorrect Kora usage. Add comments/Javadoc only if asked.
| Artifact | io.koraframework:scheduling-db-scheduler (version from io.koraframework:kora-bom) — brings com.github.kagkarlsson:db-scheduler:16.12.0 as api |
| Module | io.koraframework.scheduling.db.scheduler.DbSchedulerModule (extends io.koraframework.scheduling.common.SchedulingModule) |
| Annotations | io.koraframework.scheduling.db.scheduler.annotation.{ScheduleDbWithCron, ScheduleDbWithFixedDelay, ScheduleDbOnce} |
| Runtime | io.koraframework.scheduling.db.scheduler.KoraDbScheduler — @Root, Lifecycle, Wrapped<Scheduler> |
| Processor | Java annotationProcessor "io.koraframework:annotation-processors" · Kotlin ksp("io.koraframework:symbol-processors") |
| Needs | a javax.sql.DataSource in the graph — normally JdbcDatabaseModule (kora-database-jdbc) |
| Config roots | scheduling.dbScheduler · scheduling.telemetry · one arbitrary path per job via config = "…" |
Jobs are rows in a database table. Every replica polls the table; a due execution is picked by exactly one replica, executed, and its next execution time is written back. A restart, a deploy or a crashed node does not lose the schedule.
Coming from earlier 2.0 snapshots
This module is not in 2.0.0.RC1 — it first appeared on the 2.0 snapshot line. Code written
against an earlier snapshot needs these changes (kora-projects/kora PRs #922 and #952):
What ships with it
7 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/application.conf.template 1.1 KB
- assets/DbScheduledJobs.java.template 2.3 KB
- assets/DbScheduledJobs.kt.template 2.3 KB
- assets/V2__create_kora_scheduling_db_scheduler_jobs.sql.template 1.5 KB
- evals/evals.json 19 KB
- references/db-scheduler-config-reference.md 9.5 KB
- references/db-scheduler-reference.md 14 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.
- 16d ago First seen · 391 lines · 245 tokens per session scan A 5c49355cf5b3
kora-aop-scheduling-db is a skill published in the GitHub repository kora-projects/kora-skills (2 stars, last pushed 17d ago), licensed Apache-2.0. It adds 245 tokens to every session and 6,640 once invoked, about $0.0010 per session on Opus 5.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-10-06.
Other skills, from other repositories
horse-database-pooling
Guide for setting up thread-safe database connection pooling (FireDAC / UniDAC) in multithreaded Horse applications.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
platform-custom-field-generate
Use when users create, generate, or validate Salesforce Custom Field metadata. Trigger on custom fields, field types, Roll-Up Summary, Master-Detail/Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping picklist values per record type; also…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…
azure-resource-manager-sql-dotnet
Management plane SDK for provisioning and managing Azure SQL resources via Azure Resource Manager.