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.
npx agentmods add skills/cratis/ai/add-tracesnpx skills add Cratis/AI --skill add-tracesgit clone --depth 1 https://github.com/Cratis/AIWrote 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/cratis/ai/add-traces)<a href="https://agentmods.dev/skills/cratis/ai/add-traces"><img src="https://agentmods.dev/badge/skills/cratis/ai/add-traces.svg" alt="Measured on agentmods" 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 | $0.00073 | $0.01902 |
| Opus 5 | $0.00036 | $0.00951 |
| Sonnet 5 | $0.00015 | $0.00380 |
| Haiku 4.5 | $0.00007 | $0.00190 |
Grade A, and why
add-traces 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-traces — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding Traces to a Class
Chronicle uses the Fundamentals Traces pattern from Cratis.Traces. Never call System.Diagnostics.ActivitySource directly. Always use the source-generator [Span] attribute and IActivitySource<T>.
Overview
- Create a
*Traces.cscompanion file with[Span]methods. - Register
IActivitySource<T>viaservices.AddNamedActivitySource(WellKnown.MeterName)inChronicleMetersExtensions(one call covers all types via open-generic keyed DI). - Inject
[FromKeyedServices(WellKnown.MeterName)] IActivitySource<TTarget>into the class. - Call the generated extension methods and apply tags via
TagExtensions. - Update specs to pass
new ActivitySource<T>()(not a substitute).
DI registration architecture
Chronicle's ActivitySource follows the same keyed DI pattern as Meter:
| Layer | Meter | ActivitySource |
|---|---|---|
Shared well-known instance (keyed by WellKnown.MeterName) |
Meter("Cratis.Chronicle") |
System.Diagnostics.ActivitySource("Cratis.Chronicle") |
Per-type wrapper (keyed by WellKnown.MeterName) |
IMeter<T> / Meter<T> |
IActivitySource<T> / ActivitySource<T> |
| Registered by | services.AddNamedMeter(WellKnown.MeterName) |
services.AddNamedActivitySource(WellKnown.MeterName) |
Both calls are made from ChronicleMetersExtensions.AddChronicleMeters(). They use open-generic keyed DI (TryAddKeyedSingleton(typeof(IMeter<>), name, typeof(Meter<>))), so any new type added to a keyed-injected class is automatically covered — no per-type registration step is needed.
Step 1 — Create a *Traces.cs companion file
Each class that needs tracing gets its own *Traces.cs file in the same folder.
// 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);
}
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.
- 4d ago First seen · 200 lines · 73 tokens per session scan A 8aaebfa7a713
add-traces is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,902 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-08-31.
Other skills, from other repositories
ship-changes
Ship staged or unstaged local changes: create a branch, make logical commits, push to origin, open a PR with the correct description and label, merge it, close the issues it resolves, and delete the branch locally and on origin. Use whenever the user asks to commit, push, create a PR, ship, or land changes.
add-concept
Use this skill when asked to create a strongly-typed domain identifier or value (such as ProjectId, AuthorName, InvoiceNumber) in a Cratis-based project. Produces a ConceptAs record with the correct conversions and sentinel values.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
cratis-command
Step-by-step guidance for creating a Cratis Arc command — [Command] record, Handle() method, CommandValidator, proxy generation, and React .use() hook with CommandDialog. Use when adding or creating a command, wiring up a form or button to the backend, working with IEventLog, CommandResult, CommandValidator…
cratis-readmodel
Step-by-step guidance for creating a Cratis Chronicle read model from scratch — defining events, choosing between projection and reducer, [ReadModel] record with static query methods, and the generated TypeScript proxy in React. Use when creating a read model, working with [EventType], [ReadModel], IProjectionFor…
add-traces
Use this skill when asked to add OpenTelemetry tracing to a class in a Cratis Chronicle Kernel project. Produces Traces.cs companion files using the [Span] source-generator pattern from Cratis.Traces, registers IActivitySource as a keyed DI service, and injects it into the target class.