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-telemetry-loggingWrote 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-telemetry-logging)<a href="https://agentmods.dev/skills/kora-projects/kora-skills/kora-telemetry-logging"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-telemetry-logging/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-telemetry-logging"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-telemetry-logging.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.00070 | $0.03069 |
| Opus 5 | $0.00035 | $0.01535 |
| Sonnet 5 | $0.00014 | $0.00614 |
| Haiku 4.5 | $0.00007 | $0.00307 |
Grade A, and why
kora-telemetry-logging 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 9d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kora Telemetry Logging
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.
Kora uses slf4j-api as the logging facade for the whole framework; the recommended
implementation is Logback via LogbackModule. On top of SLF4J, Kora adds structured
arguments, a structured MDC, config-driven log levels, and the KoraAsyncAppender
for non-blocking output that correctly propagates structured MDC.
When to use
- Add Logback to a Kora service and pick text vs JSON output.
- Set per-package log levels from config (
logging.levels) instead of onlylogback.xml. - Enable per-module telemetry logging (
*.telemetry.logging.enabled). - Attach structured key/values to log records (
StructuredArgument, KoraMDC). - Log method arguments/results declaratively with
@Log, or enrich MDC with@Mdc.
Source of truth
| Topic | Path |
|---|---|
| SLF4J / Logback / structured logs / MDC | .kora-agent/kora-docs/mkdocs/docs/en/documentation/logging-slf4j.md |
@Log / @Mdc aspects |
.kora-agent/kora-docs/mkdocs/docs/en/documentation/logging-aspect.md |
| End-to-end observability guide | .kora-agent/kora-docs/mkdocs/docs/en/guides/observability.md |
| Example apps | .kora-agent/kora-examples/examples/java/kora-java-telemetry, .kora-agent/kora-examples/guides/java/kora-java-guide-observability-app |
Quick Start
1. Dependencies
The kora-parent BOM manages all Kora versions; never pin a version on an individual
ru.tinkoff.kora:* artifact. The annotation processor is mandatory.
dependencies {
koraBom platform("ru.tinkoff.kora:kora-parent:1.2.19")
annotationProcessor "ru.tinkoff.kora:annotation-processors" // Java; Kotlin: ksp "ru.tinkoff.kora:symbol-processors"
implementation "ru.tinkoff.kora:logging-logback" // SLF4J + Logback implementation, pulls in logging-common
implementation "ru.tinkoff.kora:config-hocon" // log levels live in the Kora config
}
What ships with it
16 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.logging.conf.template 1.0 KB
- assets/Application.logging.java.template 547 B
- assets/Application.logging.kt.template 582 B
- assets/build.gradle.logging.template 988 B
- assets/logback.dev.xml.template 1.1 KB
- assets/logback.json-only.xml.template 1.3 KB
- assets/logback.xml.template 1.0 KB
- assets/LoggingInterceptor.java.template 1.8 KB
- assets/LoggingService.java.template 1.9 KB
- evals/evals.json 6.6 KB
- references/async-logging-reference.md 3.7 KB
- references/json-logging-reference.md 7.4 KB
- references/logback-config-reference.md 5.6 KB
- references/logging-aspect-reference.md 4.1 KB
- references/mdc-context-reference.md 5.0 KB
- references/structured-logging-reference.md 4.8 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.
- 9d ago First seen · 298 lines · 70 tokens per session scan A 935015b460dd
kora-telemetry-logging is a skill published in the GitHub repository kora-projects/kora-skills (1 stars, last pushed 8d ago), licensed Apache-2.0. It adds 70 tokens to every session and 3,069 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
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
widget-design
Best practices for designing UI widgets in xmcp. Use when creating interactive widgets for GPT Apps or MCP Apps, choosing between React components and template literals, designing widget layouts, handling state and data fetching, or troubleshooting widget rendering issues.
therapeutic-ifs
Unified inner work engine: Schema deconstruction (diagnosis) + IFS therapy (treatment). Absorbs: schema-deconstruction.
social-physics-filter
Unified boundary enforcement, interpersonal diagnostic, and relational audit engine. Absorbs 40 psychology + 2 social protocols and all relationship case studies.
om-data-model-design
Design or change standalone module entities, relations, encryption maps, migrations, snapshots, locking, and atomic writes. Use for "add entity", "database model", "migration", "encrypt this field", "optimistic locking", "model danych", or persistence bugs.
om-troubleshooter
Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.