cratis-chronicle-client-elixir

cratis-chronicle-client-elixir is a skill for Claude Code, Codex from Cratis/AI. It costs 120 tokens per session (4,035 once invoked), scanned A, original, MIT.

A guide to using the cratis_chronicle library from an Elixir application. It covers putting the Chronicle client in an OTP supervision tree, appending events, and defining event handlers.

In plain words
What is it for?
Use it to connect an Elixir service to Chronicle, append events, and process them with reactors.
Why use it?
It clarifies that the library is an ordinary Elixir library and does not create a supervision tree for you. It also keeps guidance tied to the published version rather than unreleased code.

Skill for Claude CodeCodex

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

Good fit Use it to connect an Elixir service to Chronicle, append events, and process them with reactors.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cratis/ai/cratis-chronicle-client-elixir
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-chronicle-client-elixir
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-chronicle-client-elixir

README.md
[![agentmods](https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-client-elixir/github.svg)](https://agentmods.dev/skills/cratis/ai/cratis-chronicle-client-elixir)
Your own site
<a href="https://agentmods.dev/skills/cratis/ai/cratis-chronicle-client-elixir"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-client-elixir/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.

agentmods 80×15 button for cratis-chronicle-client-elixir

Your own site · 80×15
<a href="https://agentmods.dev/skills/cratis/ai/cratis-chronicle-client-elixir"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-client-elixir.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 120 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,035 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.00120 $0.04035
Opus 5.5 $0.00048 $0.01614
Sonnet 5.5 $0.00024 $0.00807
Haiku 4.5 $0.00012 $0.00404

Measured 3d ago against content hash d732f9356d13, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cratis-chronicle-client-elixir 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 3d 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.

.cratis/ai/skills/cratis-chronicle-client-elixir/SKILL.md · 306 lines

How it starts

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

The Chronicle client for Elixir

cratis_chronicle is a standalone client SDK. It is a library, not a framework: it starts no supervision tree of its own, you add Chronicle.Client to yours, and everything after that is ordinary OTP.

Verified product sources

Source: Cratis/Chronicle.Elixir (Hex package cratis_chronicle). Source paths below are relative to Source/chronicle/.

Read references/upgrading.md when moving an application from an older client. Requires Elixir ~> 1.18; read references/product-sources.md for the package and contracts dependency facts.

A git tag is not a Hex release. mix deps.get fetches only published versions, and the repository's VERSION file is a build-time placeholder: never quote it. Use namespaced modules (Chronicle.Events.EventType, not Chronicle.EventType); older READMEs got this wrong. Maintained snippets live in Documentation/client-snippets/.

Chronicle.Concept (use Chronicle.Concept, type: :string) is the preferred way to classify a personal value once, mirroring ConceptAs<T>; it requires cratis_chronicle 3.0.0, and an older client annotates fields with pii/1,2.

Adding it

# mix.exs
defp deps do
  [
    {:cratis_chronicle, "~> 3.13"}
  ]
end

The library declares extra_applications: [:logger, :inets, :ssl] and no mod: (Source/chronicle/mix.exs), so nothing starts on its own. :inets and :ssl back the least-connections load balancer's HTTP probes.

Starting the client

Chronicle.Client is a Supervisor (lib/chronicle/client.ex) with start_link(opts \\ []). Put it in your application's tree — this is the CI-validated snippet from Documentation/client-snippets/get-started/console/connect.md:

defmodule MyApp.Application do
  use Application

  @impl true
  def start(_type, _args) do
    children = [
      {Chronicle.Client,
       connection_string: Chronicle.Connections.ConnectionString.development(),
       event_store: "quickstart",
       otp_app: :my_app}
    ]

    Supervisor.start_link(children, strategy: :one_for_one, name: MyApp.Supervisor)
  end
end

Read the full file on GitHub · 306 lines

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. 3d ago Changed · -2 tokens per session d732f9356d13
  2. 6d ago Changed · -23 lines · +15 tokens per session 81a40a501975
  3. 7d ago Changed · -98 lines 724d6422e6b5
  4. 9d ago Changed · -4 lines · -28 tokens per session 22c58c2bb583
  5. 12d ago Changed · -79 lines caae71f834cb
  6. 1mo ago Changed · +76 lines · +23 tokens per session 10a150cec7a7
  7. 1mo ago Changed · +4 lines f02d08258b5c
  8. 1mo ago First seen · 430 lines · 112 tokens per session scan A dc97323a5070

Subscribe to this mod's changes

cratis-chronicle-client-elixir is a skill published in the GitHub repository Cratis/AI (4 stars, last pushed yesterday), licensed MIT. It adds 120 tokens to every session and 4,035 once invoked, about $0.0005 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-09-06.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens