cratis-engineering-chronicle-kernel-tracing

cratis-engineering-chronicle-kernel-tracing is a skill for Claude Code, Codex from Cratis/AI. It costs 78 tokens per session (1,962 once invoked), scanned A, original, MIT.

A contributor guide for adding OpenTelemetry tracing to the Chronicle repository. OpenTelemetry is a standard way to record spans that show how work flows through software, and Chronicle is the Cratis event-storage component.

In plain words
What is it for?
It is for instrumenting Chronicle kernel and client classes with generated spans, activity sources, and relevant trace tags.
Why use it?
It prevents maintainers from using the wrong tracing APIs or applying internal Chronicle instructions to ordinary applications.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for instrumenting Chronicle kernel and client classes with generated spans, activity sources, and relevant trace tags.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cratis/ai/cratis-engineering-chronicle-kernel-tracing
View source ↗ Cratis/AI
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Cratis/AI --skill cratis-engineering-chronicle-kernel-tracing
Clone the repo
git clone --depth 1 https://github.com/Cratis/AI

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for cratis-engineering-chronicle-kernel-tracing

README.md
[![agentmods](https://agentmods.dev/badge/skills/cratis/ai/cratis-engineering-chronicle-kernel-tracing.svg)](https://agentmods.dev/skills/cratis/ai/cratis-engineering-chronicle-kernel-tracing)
Your own site
<a href="https://agentmods.dev/skills/cratis/ai/cratis-engineering-chronicle-kernel-tracing"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-engineering-chronicle-kernel-tracing.svg" alt="Measured on agentmods" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,962 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00078 $0.01962
Opus 5 $0.00039 $0.00981
Sonnet 5 $0.00016 $0.00392
Haiku 4.5 $0.00008 $0.00196

Measured today against content hash 439b1148c28b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

cratis-engineering-chronicle-kernel-tracing 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 today.

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.

engineering/skills/cratis-engineering-chronicle-kernel-tracing/SKILL.md · 229 lines

How it starts

The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add tracing to a Chronicle class

Chronicle instruments itself with the Fundamentals traces pattern from Cratis.Traces. Never call System.Diagnostics.ActivitySource directly. Declare spans with the [Span] source generator and take an IActivitySource<T> on the class being traced.

This is contributor guidance for the Chronicle repository. An application built on Chronicle instruments itself with ordinary OpenTelemetry; nothing here applies to it.

Verified product sources

This skill is verified against these exact sources:

Package Purpose
Cratis.Fundamentals Cratis.Traces.SpanAttribute, IActivitySource<T>, IActivityScope<T>, AddNamedMeter, AddNamedActivitySource
Cratis.Chronicle (kernel and clients) ChronicleMetersExtensions, WellKnown.MeterName, the tag extensions

Confirm the pinned Cratis.Fundamentals version in the repository's package management before relying on a member.

The shape

  1. Declare the spans in a <ClassName>Traces.cs companion file.
  2. Take IActivitySource<TClass> on the class.
  3. Open a scope with the generated method and tag it.
  4. Update the specifications to supply a real activity source.

No per-type dependency-injection registration is needed — the registration is open-generic.

Step 1 — Declare the spans

Each traced class gets its own <ClassName>Traces.cs, in the same folder as <ClassName>.cs.

// Copyright (c) Cratis. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.

using System.Diagnostics;
using Cratis.Traces;

namespace Cratis.Chronicle.<Namespace>;

#pragma warning disable SA1600 // Elements should be documented
#pragma warning disable MA0048 // File name must match type name
#pragma warning disable SA1402 // File may only contain a single type

internal static partial class <ClassName>Traces
{
    [Span("cratis.chronicle.<domain>.<operation>", ActivityKind.Internal)]
    internal static partial IActivityScope<<ClassName>> <OperationName>(
        this IActivitySource<<ClassName>> source);
}

Read the full file on GitHub · 229 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. today First seen · 229 lines · 78 tokens per session scan A 439b1148c28b

Subscribe to this mod's changes

cratis-engineering-chronicle-kernel-tracing is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 1,962 once invoked, about $0.0004 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-09-06.

Related

Other skills, from other repositories

managedcode-orleans-graph

Integrate ManagedCode.Orleans.Graph into an Orleans-based .NET application for grain-call policy enforcement, deadlock detection, live-call telemetry, and Mermaid graph diagnostics. USE FOR: ManagedCode.Orleans.Graph integration; allowed grain transitions; Orleans call filters; live policy graphs; reviewing Orleans…

managedcode/dotnet-skills · 114 tokens

asynkron-profiler

Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts. USE FOR: Asynkron.Profiler setup; automation-friendly profiling output; CPU, allocation, exception, contention, and heap investigation. DO NOT…

managedcode/dotnet-skills · 122 tokens

maui-ai-debugging

Legacy DevFlow debug skill. USE FOR: maui-ai-debugging, maui devflow, screenshots, visual tree, Blazor CDP, simulator/emulator debugging. DO NOT USE FOR: setup, desktop automation, AppleScript, host xdotool.

dotnet/maui-labs · 62 tokens

architecture-paradigm-cqrs-es

Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.

athola/claude-night-market · 39 tokens

fix-feature-bug

Skill "fix-feature-bug" from markmhendrickson/neotoma, covering fix feature bug, workflow, error classification (configurable), configuration and inputs.

markmhendrickson/neotoma · 8 tokens

analyzing-code-structure

Use when editing code structure with text matching ambiguity, handling "oldstring not unique" problems, or performing formatting-independent pattern matching across function signatures, method calls, and class structures.

SebastienDegodez/copilot-instructions · 42 tokens